1 |
On Fri, 22 Dec 2006 09:16:10 +0200, Alan McKinnon wrote: |
2 |
|
3 |
> I can't believe you are advocating either of those solutions. It means |
4 |
> you retain 500M worth of tgz'ed portage tree for just in case an ebuild |
5 |
> leaves the tree. Any custom changes you make to the tree are wiped out |
6 |
> with the next --sync anyway, so now the user has to remember which ones |
7 |
> were updated and remember to put them all back. |
8 |
|
9 |
Except it's not 500MB, as you'll see by looking at the snapshots |
10 |
directory on any Gentoo mirror. Of course, the fact that portage trees |
11 |
for the last couple of weeks are nicely tarred up on all the Gentoo |
12 |
mirrors makes this process pointless anyway :) |
13 |
|
14 |
> A bin package is equally cumbersome. You will very quickly consume huge |
15 |
> amounts of disk space - at least equal to all the current packages on |
16 |
> the system plus old ones that were updated. |
17 |
|
18 |
Maybe, but they do provide an extremely useful fallback, especially for |
19 |
those of us running ~arch systems. Being able to roll back to an older, |
20 |
working version in seconds rather than minutes or hours is a definite |
21 |
benefit. |
22 |
|
23 |
> With an average notebook |
24 |
> 40G drive, that's 40% of your disk space gone right there. |
25 |
|
26 |
Which is why I have $PKGDIR on an NFS mounted drive. Desktop drives are |
27 |
big and cheap. |
28 |
|
29 |
> And the user |
30 |
> still has to remember which packages are the customized ones. |
31 |
> |
32 |
> Trust me, the portage devs have already figured all this out and |
33 |
> overlays are exactly the solution for this. The user already has to be |
34 |
> online to have updated, so all he needs do is get the desired ebuild |
35 |
> from cvs, copy it to /usr/local/portage, block updates to that package |
36 |
> using package.mask and then GO AWAY AND FORGET ALL ABOUT IT. No more |
37 |
> maintenance, no monthly tars, no vast amounts of disk space consumed. |
38 |
> it all just works. |
39 |
|
40 |
Absolutely. Overlays are there specifically for people who need something |
41 |
different from the standard portage tree. They are hardly difficult to |
42 |
use, as long as you know how to use mkdir and cp. When a user has a |
43 |
system that depends on specific versions of particular packages, all he |
44 |
has to do is copy them from /usr/portage to the overlay. You shouldn't |
45 |
even need to mess with CVS, as soon as you mask all newer versions of a |
46 |
package, you should copy its ebuild directory to your overlay to keep it |
47 |
safe. Old versions do not disappear as soon as a newer version comes out, |
48 |
unless the previous version had a serious security hole. |
49 |
|
50 |
mkdir -p /usr/local/portage/category |
51 |
cp -a /usr/portage/category/package /usr/local/portage/category |
52 |
|
53 |
How hard is that? |
54 |
|
55 |
|
56 |
-- |
57 |
Neil Bothwick |
58 |
|
59 |
If everything is coming your way then you're in the wrong lane. |