public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vaeth <vaeth@mathematik.uni-wuerzburg.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Removals reply
Date: Fri, 1 Feb 2013 18:40:32 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.1302011826300.28203@wma7001.mathematik.uni-wuerzburg.de> (raw)
In-Reply-To: <kyshH-5NF-3@gated-at.bofh.it>


> [...] and if anyone wants to start where we left he
> can pick out the ebuild from attic and put into his own overlay where
> it might work for him or even put it back to tree fixed.

And this is exactly what *cannot* be done after a while:

The ebuild is still available by CVS (or maybe git in future),
but if there were already a lot of gentoo patches, the tarball with these
patches is lost forever.  If even upstream is dead, not even the main
tarball will be available anymore.

> Go for it, i wrote exactly what to do, create vcs/tracker/homepage and 
> it can stay.

And what if somebody decides to do so in a year?
E.g. if somebody gets some hardware in a year and needs support of
a package which was removed?
Or if he was not yet a gentoo user at the time when the package was
removed (or absent/busy for a long period)?

Then he is lost unless a distribution with bigger resources as gentoo
has decided to keep the package. Not really a selling point for gentoo.


  parent reply	other threads:[~2013-02-01 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <kypjR-1W4-29@gated-at.bofh.it>
2013-02-01 16:52 ` [gentoo-dev] Removals reply Vaeth
     [not found] ` <kyqfU-34L-13@gated-at.bofh.it>
     [not found]   ` <kyshH-5NF-3@gated-at.bofh.it>
2013-02-01 17:40     ` Vaeth [this message]
2013-02-01 20:30       ` Tomáš Chvátal
     [not found] <kys82-5oT-5@gated-at.bofh.it>
     [not found] ` <kysUq-6og-21@gated-at.bofh.it>
     [not found]   ` <kysUq-6og-17@gated-at.bofh.it>
     [not found]     ` <kyvyW-1fg-11@gated-at.bofh.it>
2013-02-02 11:44       ` Vaeth
2013-02-02 12:27         ` Rich Freeman
2013-02-02 13:05         ` Tomáš Chvátal
2013-02-02 18:49           ` William Hubbs
2013-02-02 19:01             ` Rick "Zero_Chaos" Farina
     [not found] <kyJLA-1Qm-9@gated-at.bofh.it>
     [not found] ` <kyJLA-1Qm-15@gated-at.bofh.it>
     [not found]   ` <kyJLA-1Qm-7@gated-at.bofh.it>
     [not found]     ` <kyL10-3yy-19@gated-at.bofh.it>
     [not found]       ` <kyQk1-1q1-5@gated-at.bofh.it>
2013-02-03  5:07         ` Vaeth
2013-02-03  6:07           ` Alexandre Rostovtsev
2013-02-04 11:08             ` Michael Weber
2013-02-04 15:45               ` Gilles Dartiguelongue
2013-02-03  7:30           ` Alec Warner
2013-02-03 13:29           ` Rich Freeman
     [not found] <kz002-5ci-15@gated-at.bofh.it>
     [not found] ` <kz002-5ci-17@gated-at.bofh.it>
     [not found]   ` <kz002-5ci-19@gated-at.bofh.it>
     [not found]     ` <kz002-5ci-21@gated-at.bofh.it>
     [not found]       ` <kz002-5ci-23@gated-at.bofh.it>
     [not found]         ` <kz002-5ci-13@gated-at.bofh.it>
     [not found]           ` <kz2lb-7Z1-1@gated-at.bofh.it>
2013-02-03 13:18             ` Vaeth

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=alpine.LNX.2.00.1302011826300.28203@wma7001.mathematik.uni-wuerzburg.de \
    --to=vaeth@mathematik.uni-wuerzburg.de \
    --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