unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: sharlatanus@gmail.com, zimon.toutoune@gmail.com,
	othacehe@gnu.org, ludo@gnu.org, me@tobias.gr, rekado@elephly.net,
	guix@cbaines.net, 68835-done@debbugs.gnu.org
Subject: bug#68835: Resolving package inheritance issue
Date: Sun, 11 Feb 2024 23:53:17 -0500	[thread overview]
Message-ID: <875xyuwaf6.fsf@gmail.com> (raw)
In-Reply-To: <87msslzsxt.fsf@jpoiret.xyz> (Josselin Poiret's message of "Wed,  31 Jan 2024 11:41:02 +0100")

Hi Oleg,

Josselin Poiret <dev@jpoiret.xyz> writes:

> Hi Oleg,
>
> Sharlatan Hellseher <sharlatanus@gmail.com> writes:
>
>> Long story short, how to resolve package inheritance which would not
>> break CI ;-) ?
>>
>> [...]
>>
>> My rational was to keep golang module in (gnu packages golang-web) and
>> the new inherited package providing executable in (gnu packages web)
>> which introduced the regression.
>
> Please see "(guix) Cyclic Module Dependencies" in the manual, it
> contains some explanations around this kind of issue.
>
> I'd suggest not separating inherited packages in different modules.

Agreed; using lazy evaluation to alleviate cycles is our modules is
convenient; but it means we need a strict hygiene, following what's laid
out in the referenced doc section above.

I'm closing, but feel free to discuss this further if something is not
clear/could be improved.

-- 
Thanks,
Maxim




  reply	other threads:[~2024-02-12  4:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31  1:01 bug#68835: Resolving package inheritance issue Sharlatan Hellseher
2024-01-31 10:41 ` Josselin Poiret via Bug reports for GNU Guix
2024-02-12  4:53   ` Maxim Cournoyer [this message]
2024-02-01 13:27 ` Simon Tournier

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=875xyuwaf6.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=68835-done@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=guix@cbaines.net \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.org \
    --cc=rekado@elephly.net \
    --cc=sharlatanus@gmail.com \
    --cc=zimon.toutoune@gmail.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).