From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Shutdown of berlios
Date: Mon, 31 Oct 2011 14:01:56 -0400 [thread overview]
Message-ID: <CAGfcS_kn5a3m7mjTsq3u5uiRvecdfhZOqyoWs=SV2pHgk-zFFg@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr80gRFPYqQRR1jB7HFRNe7H4rKTYuu0g2h5Zu3DXhsmyA@mail.gmail.com>
On Mon, Oct 31, 2011 at 12:43 PM, Alec Warner <antarus@gentoo.org> wrote:
> We can't force people who write Gentoo specific software to host w/us
> (that would be silly.) If upstream is dead then take a tarball and
> clone it into a git repo; nothing is stopping you.
While that should certainly happen if you want to continue with
development, if the concern is that we don't lose the tarballs for the
packages in the tree the easiest solution is for the maintainers to
grab a copy and stick it in their dev web space and point the SRC_URI
there. Unless the project was already in git that is likely to be
easier than trying to re-create the same tarballs in some other repo
like github.
That is, assuming the current fashion is to host stuff like this in
dev web space. It seems like that comes and goes, but in the absence
of anything better it probably will do and beats having the files just
vanish some day.
Rich
next prev parent reply other threads:[~2011-10-31 18:02 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
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 [this message]
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='CAGfcS_kn5a3m7mjTsq3u5uiRvecdfhZOqyoWs=SV2pHgk-zFFg@mail.gmail.com' \
--to=rich0@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