From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Shutdown of berlios
Date: Sun, 30 Oct 2011 15:50:03 -0700 [thread overview]
Message-ID: <CAAr7Pr_wCd7knzceQis4qJ_qCn8zX3D6H=RsVjoYP3Djqg_nzw@mail.gmail.com> (raw)
In-Reply-To: <4EADCFC0.2030007@gentoo.org>
On Sun, Oct 30, 2011 at 3:29 PM, Petteri Räty <betelgeuse@gentoo.org> wrote:
> On 29.10.2011 12.39, Tomáš Chvátal wrote:
>
>>
>> If the upstream is dead I have no clear idea what to do, but maybe
>> infra could set-up something download.gentoo.org where we could keep
>> all the files with their sums and gpg sign from us gentoo devs to
>> ensure their validity.
>>
>
> The files should stay on our mirrors as long as ebuilds refer to them.
> When no ebuilds refer to them do we have any need for the files?
>
> Regards,
> Petteri
>
>
I think the point that is made is that you have a package that has a
dead upstream but for some reason we keep it in the tree. In that case
the only copy of the src may be on our mirrors. The real answer IMHO
is to fork it and put it on some hosting (doesn't need to be Gentoo
hosting, code.google.com / github / whatever.)
The mirrors are not designed to persist that kind of data; so folks
get upset when the only copy of the source is deleted by the mirror
service.
next prev parent reply other threads:[~2011-10-30 22:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 9:39 [gentoo-dev] Shutdown of berlios Tomáš Chvátal
2011-10-29 14:56 ` Kacper Kowalik
2011-10-29 19:09 ` [gentoo-dev] " Duncan
2011-10-29 20:06 ` [gentoo-dev] " Tomáš Chvátal
2011-10-30 22:29 ` Petteri Räty
2011-10-30 22:50 ` Alec Warner [this message]
2011-10-31 13:09 ` [gentoo-dev] " Diego Elio Pettenò
2011-10-31 16:43 ` Alec Warner
2011-10-31 17:39 ` [gentoo-dev] " Diego Elio Pettenò
2011-10-31 17:57 ` [gentoo-dev] " Francisco Blas Izquierdo Riera (klondike)
2011-10-31 18:01 ` Rich Freeman
2011-11-01 0:52 ` [gentoo-dev] " Diego Elio Pettenò
2011-10-31 21:16 ` [gentoo-dev] " Duncan
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='CAAr7Pr_wCd7knzceQis4qJ_qCn8zX3D6H=RsVjoYP3Djqg_nzw@mail.gmail.com' \
--to=antarus@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