public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Removals reply
Date: Sun, 03 Feb 2013 01:07:58 -0500	[thread overview]
Message-ID: <1359871678.23785.25.camel@rook> (raw)
In-Reply-To: <alpine.LNX.2.00.1302030520260.4428@wma7001.mathematik.uni-wuerzburg.de>

On Sun, 2013-02-03 at 06:07 +0100, Vaeth wrote:
> So this 30 day delay will enable these people to get involved,
> especially for all the packages which were removed in the last years?
> Now it is apparent that an archive for dropped packages (in the
> form of keeping masked packages or some other form) is not needed:
> I want to join your club with the time machine!

If you want an automatic archive for dropped packages, MAKE ONE! Get a
domain name, rent a VPS with lots of disc space, subscribe a mail
account to gentoo-dev, write a small script that parses last-rites
announcements and automatically archives the affected ebuilds and their
sources.

You have to realize that there are only three ways to get something done
in the non-commercial open-source space:
1. convince someone else that it's fun;
2. convince someone else that it's important; or
3. do it yourself.

We the Gentoo developers strongly believe that this project is not fun
and not important. So if want dropped packages to be automatically
archived, I suggest that you volunteer for the job of automatically
archiving them.

-Alexandre.




  reply	other threads:[~2013-02-03  6:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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         ` [gentoo-dev] Removals reply Vaeth
2013-02-03  6:07           ` Alexandre Rostovtsev [this message]
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
     [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] <kypjR-1W4-29@gated-at.bofh.it>
2013-02-01 16:52 ` 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
2013-02-01 20:30       ` Tomáš Chvátal

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=1359871678.23785.25.camel@rook \
    --to=tetromino@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