GNU bug report logs - #68835
Resolving package inheritance issue

Previous Next

Full log

Message #16 received at 68835-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: sharlatanus <at> gmail.com, zimon.toutoune <at> gmail.com, othacehe <at> gnu.org,
 ludo <at> gnu.org, me <at> tobias.gr, rekado <at> elephly.net, guix <at> cbaines.net,
 68835-done <at> debbugs.gnu.org
Subject: Re: bug#68835: Resolving package inheritance issue
Date: Sun, 11 Feb 2024 23:53:17 -0500

Hi Oleg,

Josselin Poiret <dev <at> jpoiret.xyz> writes:

> Hi Oleg,
>
> Sharlatan Hellseher <sharlatanus <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.