Re: Policy to remove obsolete packages

2019-02-08 Thread Björn Höfling
Hi simon, On Thu, 7 Feb 2019 13:40:53 +0100 zimoun wrote: > Hi, > > I understand but I am not sure to see the points and/or advantages > about a policy. > > From my opinion, obsolete package is not well-defined and define > cleanly what an obsolete package is will be bikeshedding. :-) > And

Re: Policy to remove obsolete packages

2019-02-07 Thread swedebugia
On 2019-02-06 23:32, Ricardo Wurmus wrote: This is a tangent. This thread is about removing obsolete packages. Let’s not discuss moving packages each to their own module here. This has been discussed elsewhere and it’s a can of worms (which is fine if you’re a bird, but not so good if you want

Re: Policy to remove obsolete packages

2019-02-07 Thread zimoun
Hi, I understand but I am not sure to see the points and/or advantages about a policy. >From my opinion, obsolete package is not well-defined and define cleanly what an obsolete package is will be bikeshedding. :-) And I think that deprecated should come from upstream. However, a popcon of the do

Re: Policy to remove obsolete packages

2019-02-07 Thread Ricardo Wurmus
swedebugia writes: > I like the idea of keeping it simple and now we tried the lumped > modules approach. I don't like it so much to be honest. > > It comes with obvious drawbacks when the package per file grow and > subcategorization have to be done. > > But is it efficient in guile to load hu

Re: Policy to remove obsolete packages

2019-02-05 Thread ng0
swedebugia transcribed 6.9K bytes: > n...@n0.is skrev: (5 februari 2019 22:31:53 CET) > >Bjrn Hfling transcribed 846 bytes: > >> On Mon, 04 Feb 2019 23:52:47 +0100 > >> Ludovic Courtès wrote: > >> > >> > >> > (Note that, IIUC, in openSuSE a package can be broken and yet > >remain > >> > installa

Re: Policy to remove obsolete packages

2019-02-05 Thread swedebugia
n...@n0.is skrev: (5 februari 2019 22:31:53 CET) >Bjrn Hfling transcribed 846 bytes: >> On Mon, 04 Feb 2019 23:52:47 +0100 >> Ludovic Courtès wrote: >> >> >> > (Note that, IIUC, in openSuSE a package can be broken and yet >remain >> > installable by users, because the last binary that was produc

Re: Policy to remove obsolete packages

2019-02-05 Thread ng0
Bjrn Hfling transcribed 846 bytes: > On Mon, 04 Feb 2019 23:52:47 +0100 > Ludovic Courtès wrote: > > > > (Note that, IIUC, in openSuSE a package can be broken and yet remain > > installable by users, because the last binary that was produced is > > still around.) > > We have guix pull --commit=

Re: Policy to remove obsolete packages

2019-02-05 Thread Björn Höfling
On Tue, 5 Feb 2019 00:47:42 +0100 zimoun wrote: > To me the question is more about how to automatically detect that a > patch breaks another package than a policy to remove a broken package. > > I mean if we are able to automatically detect 6 months later that a > package is broken, why are we n

Re: Policy to remove obsolete packages

2019-02-05 Thread Björn Höfling
On Mon, 04 Feb 2019 23:52:47 +0100 Ludovic Courtès wrote: > (Note that, IIUC, in openSuSE a package can be broken and yet remain > installable by users, because the last binary that was produced is > still around.) We have guix pull --commit=..., inferiors, channels and time-travel, so there ar

Re: Policy to remove obsolete packages

2019-02-04 Thread zimoun
Dear, I agree too on the policy. On Mon, 4 Feb 2019 at 23:26, Leo Famulari wrote: > > It might be tricky to know when a package has failed to build for 6 > months. Do we keep build farm evaluations for that long? Can we automate > failure notifications after a certain date? I agree. To me the q

Re: Policy to remove obsolete packages

2019-02-04 Thread Ludovic Courtès
Hi! Björn Höfling skribis: > In the FOSDEM-talk by Frederic Crozat (SuSE) about Distributions, he > mentioned their approach which I find good to adapt: > > > If a package is broken for more than 6 months, we should just remove it > from Guix. Prior to removing, we should announce on the dev mai

Re: Policy to remove obsolete packages

2019-02-04 Thread Leo Famulari
On Mon, Feb 04, 2019 at 07:06:35PM +0100, Andreas Enge wrote: > On Mon, Feb 04, 2019 at 12:16:12PM +0100, Björn Höfling wrote: > > If a package is broken for more than 6 months, we should just remove it > > from Guix. Prior to removing, we should announce on the dev mailing > > list, maybe someone

Re: Policy to remove obsolete packages

2019-02-04 Thread Andreas Enge
On Mon, Feb 04, 2019 at 12:16:12PM +0100, Björn Höfling wrote: > If a package is broken for more than 6 months, we should just remove it > from Guix. Prior to removing, we should announce on the dev mailing > list, maybe someone will care about it then. If there is no response > within 2 weeks, we

Re: Policy to remove obsolete packages

2019-02-04 Thread Pjotr Prins
On Mon, Feb 04, 2019 at 12:16:12PM +0100, Björn Höfling wrote: > Hi Guix, > > on Guix-Days we had no more time in the QA track to talk about obsolete > packages. > > In the FOSDEM-talk by Frederic Crozat (SuSE) about Distributions, he > mentioned their approach which I find good to adapt: > > >

Policy to remove obsolete packages

2019-02-04 Thread Björn Höfling
Hi Guix, on Guix-Days we had no more time in the QA track to talk about obsolete packages. In the FOSDEM-talk by Frederic Crozat (SuSE) about Distributions, he mentioned their approach which I find good to adapt: If a package is broken for more than 6 months, we should just remove it from Guix.