From: Lars Wendler <polynomial-c@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: rich0@gentoo.org
Subject: Re: [gentoo-dev] keep a gen 2013 snapshot on mirrors
Date: Thu, 14 Nov 2013 14:19:55 +0100 [thread overview]
Message-ID: <20131114141955.1bbd6ef7@shanghai.paradoxon.rec> (raw)
In-Reply-To: <CAGfcS_kg2u=v6uXdYjQUvUFmkOTdJV0imfX1tgj+v+poP=a0UA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Am Wed, 13 Nov 2013 14:12:24 -0500
schrieb Rich Freeman <rich0@gentoo.org>:
> On Wed, Nov 13, 2013 at 1:58 PM, Francesco R. <vivo75@gmail.com>
> wrote:
> >
> > long story short
> > having a portage-20130126.tar.bz2 snapshot (before the EAPI 5
> > switch) greatly simplified the upgrade of an old server on a client.
> >
> > Why not keep a copy on the servers? I mean
> > http://distfiles.gentoo.org/snapshots/
> >
>
> Going back in time with portage is the easy part - it is in CVS.
>
> The real problem is all the distfiles themselves, especially things
> like out-of-tree patch tarballs hosted by devs.
IMHO not even the worst problems as long as devs stop removing files
they consider as "deprecated" or "old". I keep everything in my
dev-space I ever put in an ebuild that landed in our official portage
tree. Of course this only works as long as you reference that place in
the affected ebuilds. Once you go the route to use mirror://gentoo in
ebuilds as SRC_URI people are screwed as soon as the ebuild vanishes
from portage.
I'd love to see this (mis-)behavior being more vigorously discouraged
in Gentoo-land...
Cheers
--
Lars Wendler
Gentoo package maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-14 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 18:58 [gentoo-dev] keep a gen 2013 snapshot on mirrors Francesco R.
2013-11-13 19:12 ` Rich Freeman
2013-11-13 20:49 ` Roy Bamford
2013-11-13 21:18 ` Rich Freeman
2013-11-15 13:17 ` [gentoo-dev] " Duncan
2013-11-15 13:38 ` Rich Freeman
2013-11-15 15:24 ` Duncan
2013-11-15 15:59 ` Peter Stuge
2013-11-14 0:27 ` [gentoo-dev] " Tom Wijsman
2013-11-14 13:17 ` Francesco R.
2013-11-14 14:01 ` Rich Freeman
2013-11-14 13:19 ` Lars Wendler [this message]
2013-11-14 19:49 ` Ian Stakenvicius
2013-11-13 19:16 ` Rick "Zero_Chaos" Farina
2013-11-14 4:38 ` Johann Schmitz
2013-11-14 13:09 ` Francesco R.
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=20131114141955.1bbd6ef7@shanghai.paradoxon.rec \
--to=polynomial-c@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=rich0@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