Hi Oleg, Josselin Poiret <d...@jpoiret.xyz> writes:
> Hi Oleg, > > Sharlatan Hellseher <sharlata...@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
