all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Roman Scherer <roman.scherer@burningswell.com>
Cc: help-guix@gnu.org
Subject: Re: Help updating CLOG
Date: Mon, 09 Sep 2024 12:43:01 +0000	[thread overview]
Message-ID: <87mskhroa2.fsf@kitej> (raw)
In-Reply-To: <861q1wlwah.fsf@burningswell.com> (Roman Scherer's message of "Fri, 06 Sep 2024 15:57:26 +0200")

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

Hi.

It looks like the "clog/docs" and "clog/tools" systems are defined in
the "clog.asd" file in the sbcl-clog package and also in the
sbcl-clog-docs and sbcl-clog-tools packages. This may be the cause of
the issue.

I suppose you separated "clog/docs" and "clog/tools" systems in their
own packages to break the dependency cycles
  "clog/tools" -> "clog-ace" -> "clog"
and
  "clog/tools" -> "clog-terminal" -> "clog"

However "clog/docs" is not in the cycles, so I think you could build
it directly in the sbcl-clog package with
  #:asd-systems '("clog" "clog/docs")
and also updating the 'delete-files' phase not to remove the files
required by "clog/docs".

Now, concerning the "clog/tools" system, I would try to delete things
related to it from the sbcl-clog package, and remove the things not related
to it from the sbcl-clog-tools package. So the sbcl-clog-tools package
would only have the "tools" directory and a ".asd" file containing only
the definition of the "clog/tools" system.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2024-09-09 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 13:57 Help updating CLOG Roman Scherer
2024-09-09 12:43 ` Guillaume Le Vaillant [this message]
2024-09-12 17:24   ` Roman Scherer
2024-09-12 17:31   ` Roman Scherer
2024-09-26 12:57     ` Guillaume Le Vaillant
2024-09-26 15:03       ` Roman Scherer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mskhroa2.fsf@kitej \
    --to=glv@posteo.net \
    --cc=help-guix@gnu.org \
    --cc=roman.scherer@burningswell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.