From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Shutdown of berlios
Date: Mon, 31 Oct 2011 09:43:59 -0700 [thread overview]
Message-ID: <CAAr7Pr80gRFPYqQRR1jB7HFRNe7H4rKTYuu0g2h5Zu3DXhsmyA@mail.gmail.com> (raw)
In-Reply-To: <1320066596.10062.38.camel@raven.home.flameeyes.eu>
On Mon, Oct 31, 2011 at 6:09 AM, Diego Elio Pettenò
<flameeyes@gentoo.org> wrote:
> Il giorno sab, 29/10/2011 alle 11.39 +0200, Tomáš Chvátal ha scritto:
>> app-text/unpaper/unpaper-0.3.ebuild:SRC_URI="mirror://berlios/${PN}/${P}.tar.gz"
>
> Removed unpaper-0.3 (I mirror a copy of the sources on my website, but I
> expect 0.4 to make muuuch more sense, since I've taken it over).
>
>> app-portage/conf-update/conf-update-1.0.1.ebuild:SRC_URI="mirror://berlios/${PN}/${P}.tar.bz2"
>> app-portage/eix/eix-0.22.11.ebuild:SRC_URI="mirror://berlios/${PN}/${P}.tar.xz"
>> app-portage/eix/eix-0.22.5.ebuild:SRC_URI="mirror://berlios/${PN}/${P}.tar.xz"
>> app-portage/eix/eix-0.23.1.ebuild:SRC_URI="mirror://berlios/${PN}/${P}.tar.xz"
>> app-portage/eix/eix-0.23.2.ebuild:SRC_URI="mirror://berlios/${PN}/${P}.tar.xz"
>> app-portage/etc-proposals/etc-proposals-1.4.3-r2.ebuild:SRC_URI="mirror://berlios/${PN}/${P}.tar.gz"
>
> And this is what makes me concerned about using external resources for
> Gentoo-specific software... I suppose we should mirror these somewhere
> on Gentoo infra, given that we're probably the only ones interested in
> it. Volunteers?
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.
>
> For future reference: I'm striving to keep a local copy of any source
> file that Portage referenced and that I could fetch (that means even
> stuff that is mirror-restricted since I only fetch it and store it
> locally, not redistribute it), at least for the time my tinderbox has
> been running... so if you happen to stumble across this after Berlios
> shut down and you need some source file that was there, feel free to get
> in touch with me. Expect some latency though.
>
> --
> Diego Elio Pettenò — Flameeyes
> http://blog.flameeyes.eu/
>
next prev parent reply other threads:[~2011-10-31 16:44 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 [this message]
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=CAAr7Pr80gRFPYqQRR1jB7HFRNe7H4rKTYuu0g2h5Zu3DXhsmyA@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