From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] the graveyard overlay
Date: Fri, 8 Jul 2016 18:33:35 +0300 [thread overview]
Message-ID: <20160708183335.259f107e46a489b8caecc790@gentoo.org> (raw)
In-Reply-To: <20160708151145.GB12325@whubbs1.gaikai.biz>
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]
On Fri, 8 Jul 2016 10:11:45 -0500 William Hubbs wrote:
> I'm starting a new thread so this will be a completely separate
> discussion.
>
> On Fri, Jul 08, 2016 at 05:56:04PM +0300, Andrew Savchenko wrote:
> > On Fri, 8 Jul 2016 10:42:14 -0400 Rich Freeman wrote:
> > > On Fri, Jul 8, 2016 at 10:30 AM, Anthony G. Basile <blueness@gentoo.org> wrote:
> > > >
> > > > Also there's some debate in IRC about whether or not these packages
> > > > should be lastrited or dropped to maintainer-needed. These forks are
> > > > not in good shape upstream, so I think it makes better sense to
> > > > p.mask/lastrite and then move them to the graveyard overlay when I
> > > > remove them from the tree in 30 days.
> > > >
> > >
> > > IMO the criteria should be whether they work or not. Not whether
> > > upstream is more or less active.
> > >
> > > If they're blockers on other work, by all means cull them. However,
> > > if the biggest problem with them is that they're using a few inodes in
> > > the repo, then they should probably stay.
> >
> > +1
> >
> > Best regards,
> > Andrew Savchenko
>
> There is also an overlay for packages that are removed from the official
> tree [1], and imo that is where old software should go if it doesn't
> have an active maintainer.
>
> I don't know why we haven't been using this, but using it more than we
> have makes a lot of sense.
When software is in the main tree, it is a subject of tree-wide
changes like GLEP 67 update, package moves and so on. In a
separated overlay it will be completely abandoned and it may create
inter-overlay dependencies issues (e.g. when A is an old
package from the tree and package B from some overlay depends on A,
so if A will move to graveyard, B will be broken).
I completely do not understand why having "old" software in tree is
a problem, if such software have no serious issues and is not
blocking major progress. If software _is_ sufficiently broken, then
indeed move it to graveyard.
As I said yesterday on IRC, one of the greatest virtues of Gentoo
is its ample spectra of packages available in the main tree. I do
not understand why it should be killed for nothing.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-08 15:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 15:11 [gentoo-dev] the graveyard overlay William Hubbs
2016-07-08 15:33 ` Andrew Savchenko [this message]
2016-07-08 16:51 ` Michał Górny
2016-07-08 17:19 ` Rich Freeman
2016-07-08 18:22 ` Chí-Thanh Christopher Nguyễn
2016-07-08 18:30 ` Rich Freeman
2016-07-08 18:51 ` Chí-Thanh Christopher Nguyễn
2016-07-08 19:08 ` Rich Freeman
2016-07-08 18:21 ` james
2016-07-08 17:53 ` james
2016-07-08 15:55 ` [gentoo-dev] " »Q«
2016-07-08 16:17 ` Andrew Savchenko
2016-07-08 18:30 ` William Hubbs
2016-07-08 20:47 ` Neil Bothwick
2016-07-08 20:21 ` [gentoo-dev] " Philip Webb
2016-07-08 21:50 ` Alec Warner
2016-07-09 1:09 ` Alec Warner
2016-07-09 13:12 ` Philip Webb
2016-07-09 15:08 ` james
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=20160708183335.259f107e46a489b8caecc790@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox