From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Policy to remove obsolete packages
Date: Mon, 4 Feb 2019 23:18:04 +0100 [thread overview]
Message-ID: <20190204221804.GA8806@jasmine.lan> (raw)
In-Reply-To: <20190204180635.GB8736@jurong>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
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 will care about it then. If there is no response
> > within 2 weeks, we really remove it.
>
> We were both in the talk and had the same reaction, so indeed I agree.
I agree with this as well.
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?
But, it's not so important whether or not it has been exactly 6 months.
At a certain point we know it's been too long and that the package is
not useful anymore.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-04 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 11:16 Policy to remove obsolete packages Björn Höfling
2019-02-04 11:51 ` Pjotr Prins
2019-02-04 18:06 ` Andreas Enge
2019-02-04 22:18 ` Leo Famulari [this message]
2019-02-04 23:47 ` zimoun
2019-02-05 10:24 ` Björn Höfling
2019-02-07 12:40 ` zimoun
2019-02-08 8:47 ` Björn Höfling
2019-02-04 22:52 ` Ludovic Courtès
2019-02-05 10:13 ` Björn Höfling
2019-02-05 21:31 ` ng0
2019-02-05 22:47 ` swedebugia
2019-02-05 23:52 ` ng0
2019-02-06 22:32 ` Ricardo Wurmus
2019-02-07 12:42 ` swedebugia
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=20190204221804.GA8806@jasmine.lan \
--to=leo@famulari.name \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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.