From: "Francesco R." <vivo75@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] keep a gen 2013 snapshot on mirrors
Date: Thu, 14 Nov 2013 14:17:15 +0100 [thread overview]
Message-ID: <5284CD5B.50502@gmail.com> (raw)
In-Reply-To: <CAGfcS_kg2u=v6uXdYjQUvUFmkOTdJV0imfX1tgj+v+poP=a0UA@mail.gmail.com>
Il 13/11/2013 20:12, Rich Freeman ha scritto:
> 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.
>
> Rich
Rich, that made me smile, none of my remote machine has cvs since a
_very_ long time say 2006.
We are speaking of box that have troubles to emerging anything new, plus
me and most of the internet barely remember cvs up :)
I do highly appreciate the suggestion to keep a @system distfiles
snapshot (once a year + portage snapshot would be a bone), but that it's
not strictly needed, just a 40MB bzipped files on a public directory and
maybe some change to the cron that wipe old files.
cheers,
Francesco R.
next prev parent reply other threads:[~2013-11-14 13:17 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. [this message]
2013-11-14 14:01 ` Rich Freeman
2013-11-14 13:19 ` Lars Wendler
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=5284CD5B.50502@gmail.com \
--to=vivo75@gmail.com \
--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