| 1 |
On Thu, Nov 14, 2013 at 8:17 AM, Francesco R. <vivo75@×××××.com> wrote: |
| 2 |
> Rich, that made me smile, none of my remote machine has cvs since a |
| 3 |
> _very_ long time say 2006. |
| 4 |
> We are speaking of box that have troubles to emerging anything new, plus |
| 5 |
> me and most of the internet barely remember cvs up :) |
| 6 |
|
| 7 |
You don't need to run cvs on the box that you're trying to update. |
| 8 |
Just run it on a different box and create a tarball of the resulting |
| 9 |
tree. |
| 10 |
|
| 11 |
I couldn't tell you what the syntax for doing that is offhand, but I |
| 12 |
imagine that it wouldn't take you much longer than it would take me to |
| 13 |
read the manpage and figure it out. If you're really stuck I'm sure |
| 14 |
somebody would help you. |
| 15 |
|
| 16 |
> |
| 17 |
> I do highly appreciate the suggestion to keep a @system distfiles |
| 18 |
> snapshot (once a year + portage snapshot would be a bone), but that it's |
| 19 |
> not strictly needed, just a 40MB bzipped files on a public directory and |
| 20 |
> maybe some change to the cron that wipe old files. |
| 21 |
|
| 22 |
Personally I'd prefer to see a more standardized way of handling |
| 23 |
non-upstream distfiles as well (probably not a tarball). However, |
| 24 |
Gentoo really isn't one of those distros that is ever going to be easy |
| 25 |
to upgrade in-place if you only do it once a year or less often. |
| 26 |
There are ways to do it, but they're going to be painful. |
| 27 |
|
| 28 |
Rich |
Archives