unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
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, 04 Feb 2019 23:52:47 +0100	[thread overview]
Message-ID: <87munbkvy8.fsf@gnu.org> (raw)
In-Reply-To: <20190204100318.208254da@alma-ubu> ("Björn Höfling"'s message of "Mon, 4 Feb 2019 12:16:12 +0100")

Hi!

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> 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 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?

I believe a policy along these lines would make sense.

(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.)

Ludo’.

  parent reply	other threads:[~2019-02-04 22:55 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
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 [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87munbkvy8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).