public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeff Horelick <jdhore@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] RFC: Graveyard project
Date: Thu, 14 Feb 2013 17:21:28 -0500	[thread overview]
Message-ID: <CAFhp8z43+wbkds3yJOSxWEy0b7SqXjDdPoVec+BgugVqUu9H7Q@mail.gmail.com> (raw)
In-Reply-To: <511D5D6D.9010608@gentoo.org>

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

On 14 February 2013 16:55, Rick "Zero_Chaos" Farina <zerochaos@gentoo.org>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/14/2013 04:31 AM, Ben de Groot wrote:
> > Hi guys and girls,
> >
> > We hereby announce the formation of the Graveyard project [1]. It aims
> > to provide users with an overlay for packages removed from portage.
> > Users are expressly invited to partake in this project, to help
> > maintain the graveyard overlay [2]. We will also help organize a
> > central space to host distfiles that are no longer mirrored by Gentoo
> > and have a broken upstream link. We use the #gentoo-dev-help channel
> > on Freenode for coordination, as well as our project space on the wiki
> > [3].
>
> What exactly is wrong with the current cvs attic space? I've salvaged
> old ebuilds and it was a completely painless process.
>
> Things that have been treecleaned were not just haphazardly removed,
> there is typically very good (often security or complete build failure
> related) reasons for this to happen.  Running an overlay of old,
> outdated, unbuildable, security vulnerable software... I know there is
> no formal process for rejecting a gentoo project but even this idea
> makes me want to get council approval for an extension to the gentoo
> project guidelines.
>
> If users want to salvage things from the cvs attic and put them into
> SUNRISE after fixing them up I'm fine with it, but the whole idea of
> this is bad for gentoo developers, bad for gentoo users, bad for gentoo
> image, I just don't see a single advantage to this and so many
> disadvantages.
>
> Please, this needs to not happen.
>
> Thanks,
> Zero
>
>
> > Please feel free to join us!
> >
> > 1: http://www.gentoo.org/proj/en/graveyard/
> > 2: https://github.com/gentoo/graveyard
> > 3: https://wiki.gentoo.org/wiki/Project:Graveyard
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJRHV1tAAoJEKXdFCfdEflK36YP/j3nXMjBUChv4a/HRVRZbK0P
> gEPxljhHLueKpebZfZWG2i/G5RoYT5QTzDpi146+xcKxYxypjnY4EfA3O5erXN7g
> rF2j8Ij8Xn4OprxDr+3+l3ojAbr+AMsyteU7jQiXEccN0n/8bDLJ1WaKa+hgy46u
> pWP7zm+Mi2S2ZYHuDgH7HbVadC1fyD7IB9heRXdfwuPT6lPA1pgu/jOibMZog2Uh
> DJlBx1emDyXt3k/noyFuDiumfNdRAwg6BegrWBuQHFNk0m8ZYiYxuuYFic/a8aRh
> Yz0MHsZC+FQd4dx3aDkrHNLJLszWHjyrn9shgtVp7aVu/T3rM9H2BHOZCC00ZtHC
> sLkMP69167YaE3UToxAA7eHQpylDBa/maJTHGFZVnz5mV8SzeOjX4ikDkfwNEUuS
> LpblNRZHuTDLnDWY6SJWFDK++JDqtAnPXWLAEDqEfEluMC76MVbTdhqjqvNBN8zQ
> lMjPTmQ/lihKR4a6LsCCkspmlEv6o4pKqWjghytqDAJuqsA1rIgKaInUPvOfCkCR
> 5Azl1KyIWL8oUA2OrhZdDvRd4hUlt3mJSEBcx6HC4Oj2NwtmM16zBwSJc3WKt7JC
> irk6D2gunFef8z1tcs/SE51lKnW+pFYIMbhyvWtumszZx/dLhu5t78KQe/8vLHnI
> S0R5VGULwVZkKVtSiRQK
> =mjOM
> -----END PGP SIGNATURE-----
>
>

IMO, all these reasons are solved by the statement: "This is why it will be
an OVERLAY and there will be no stable packages even if they were stable in
the tree before masking for removal". Packages that have tons of security
issues or do not build whatsoever will obviously not be added (unless
someone wants to give us a patch or 2 to solve those problems). Sunrise is
the wrong place for stuff that still works. Sunrise is about stuff incoming
to the tree (hopefully eventually) not outgoing from the tree.

The reason for this overlay is for packages like: media-tv/ivtv and
net-wireless/at76c503a which seem to be masked for removal because they're
deprecated and likely still work. Perhaps a user is having problems with
the driver that replaced either of these and is still using th old one
since it works fine for his hardware. There are tons of good reasons to
keep old packages around, yes a few possible bad ones as well, but that's
the case with almost anything.

[-- Attachment #2: Type: text/html, Size: 4626 bytes --]

  parent reply	other threads:[~2013-02-14 22:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB9SyzSBQcgL6rxDHcoo-O+3=K_b1iG15i2P3esj=WPjOLxivQ@mail.gmail.com>
2013-02-14 21:55 ` [gentoo-dev] Re: [gentoo-dev-announce] RFC: Graveyard project Rick "Zero_Chaos" Farina
2013-02-14 22:17   ` Ian Stakenvicius
2013-02-14 22:21   ` Jeff Horelick [this message]
2013-02-14 22:47   ` Florian Philipp
2013-02-15  0:06     ` Diego Elio Pettenò
2013-02-15  0:15       ` Rich Freeman
2013-02-15  0:19         ` Diego Elio Pettenò
2013-02-15  1:18           ` Rich Freeman
2013-02-15  1:39             ` Diego Elio Pettenò
2013-02-15  1:56               ` Peter Stuge
2013-02-15  2:20                 ` Diego Elio Pettenò
2013-02-15  2:44                   ` Peter Stuge
2013-02-15  8:15           ` Florian Philipp
2013-02-15  9:39           ` Markos Chandras
2013-02-15 12:48             ` Cyprien Nicolas
2013-02-15 13:10               ` Cyprien Nicolas
2013-02-15 13:48                 ` Ian Stakenvicius
2013-02-15 14:33                   ` Ben Kohler
2013-02-15  9:44           ` Alec Warner
2013-02-15 14:34             ` Diego Elio Pettenò
2013-02-16  4:53               ` Ben de Groot
2013-02-15 10:33           ` Alexander Berntsen
2013-02-15 12:58             ` Diego Elio Pettenò
2013-02-15 13:08               ` Alexander Berntsen

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=CAFhp8z43+wbkds3yJOSxWEy0b7SqXjDdPoVec+BgugVqUu9H7Q@mail.gmail.com \
    --to=jdhore@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