unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Policy to remove broken packages
Date: Sat, 20 Jun 2020 11:24:31 +0100	[thread overview]
Message-ID: <87v9jm6nmo.fsf@cbaines.net> (raw)
In-Reply-To: <86y2oisj41.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]


zimoun <zimon.toutoune@gmail.com> writes:

> Dear,
>
> After Guix Days 2019, the idea of having an informal policy to remove
> broken packages had emerged.  Quoting the initial Björn's message [1]:
>
>         > 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.
>
> And we all agreed. :-)
>
> How to make it happen?  Where is the correct place to mark list them:
> Data Service or Cuirass?
>
>
> 1: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00019.html

Do you have any examples of packages that are currently broken, and
which you'd like to remove?

My general views on broken packages is that it would be helpful to have
more information at the time changes are being made, like big version
upgrades. That might allow less things to be broken, or work arounds to
be put in place before things are broken, rather than trying to find
someone to fix the package after 6 months.

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2020-06-20 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 23:58 Policy to remove broken packages zimoun
2020-06-20 10:24 ` Christopher Baines [this message]
2020-06-20 10:37   ` Pierre Neidhardt
2020-06-22 15:14   ` Jack Hill
2020-06-22 17:06     ` Christopher Baines
2020-06-22 18:45       ` Leo Famulari

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=87v9jm6nmo.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).