all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Policy to remove obsolete packages
Date: Mon, 4 Feb 2019 12:51:13 +0100	[thread overview]
Message-ID: <20190204115113.vhg5pbmc5byfpjmj@thebird.nl> (raw)
In-Reply-To: <20190204100318.208254da@alma-ubu>

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:
> 
> 
> 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.
> 
> What do you think?

+1.

It would also be nice to add an OBSOLETE/DEPRECATE tag or comment
which can be removed when a package works again. This could be made
visible as metadata. Maybe even link it with debbugs.

Pj.

  reply	other threads:[~2019-02-04 11:57 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 [this message]
2019-02-04 18:06 ` Andreas Enge
2019-02-04 22:18   ` Leo Famulari
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=20190204115113.vhg5pbmc5byfpjmj@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --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.