1 |
On Fri, 24 Apr 2009 21:14:21 +0000 (UTC) |
2 |
Duncan <1i5t5.duncan@×××.net> wrote: |
3 |
|
4 |
> |
5 |
> Second, I'll mention what has become my favorite under-appreciated |
6 |
> portage feature, FEATURES=buildpkg. This creates binpkgs (in /usr/ |
7 |
> portage/package by default, see the make.conf and portage manpages for |
8 |
> details on changing this and other settings) of everything you emerge. |
9 |
> Total additional space required, 3-4 gigs (you can do it in 2 gigs but |
10 |
> it's tight). But after you've accumulated binpkgs of everything on your |
11 |
> system, if you upgrade something and it doesn't work, no sweat, just |
12 |
> emerge --pkgonly the old working version. |
13 |
> |
14 |
|
15 |
This is something that I will definitely implement. Most updates should |
16 |
be unproblematic, but it's always good to have some insurance. |
17 |
|
18 |
What I would really like to have, though, is a way to get portage to |
19 |
recognize packages that I have installed myself. There are certain cases |
20 |
where I prefer to manually compile a library or utility. When I do so, |
21 |
portage will fail to recognize this and may try to automatically recompile |
22 |
the installed package if it is a dependency for some other package. |
23 |
Invoking emerge with --nodeps can avoid this problem, unless there are |
24 |
yet other dependencies that I would like portage to automatically resolve. |
25 |
|
26 |
Some may argue that it is best to let portage handle everything and not |
27 |
interfere, but I have considerable experience in maintaining a Linux |
28 |
system and I know what can be safely done. The few packages that I |
29 |
prefer to compile myself will not muck things up for me. |
30 |
|
31 |
From what I've read in the Gentoo manuals, there does not seem to be |
32 |
a way to signal to portage that a certain package has been separately |
33 |
installed. In my opinion, something like this could be useful for |
34 |
some users. |
35 |
|
36 |
Frank Peters |