| 1 |
James wrote: |
| 2 |
> Dale<rdalek1967<at> gmail.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
> |
| 6 |
>>> Besides gcc, what is a good list |
| 7 |
>>> of critical software to use guickpkg |
| 8 |
>>> as to keep backup binaries? |
| 9 |
>>> |
| 10 |
> |
| 11 |
> |
| 12 |
>> FEATURES="buildpkg sandbox fixpackages parallel-fetch --keep-going" |
| 13 |
>> |
| 14 |
> I saw this (FEATURES="buildpkg") googling around. |
| 15 |
> |
| 16 |
> 1. What is a good list of software to use buildpkg on? |
| 17 |
> |
| 18 |
> 2. Once you decide those packages, where do you put |
| 19 |
> the list? |
| 20 |
> |
| 21 |
> Surely I do not wish to use buildpkg on every installed |
| 22 |
> package, a few or maybe the entire @system. I have not |
| 23 |
> found the answer to [1] or [2]. |
| 24 |
> |
| 25 |
> This is muddy, because supposedly the "profile" |
| 26 |
> is suppose to protect the key packages for --depclean ? |
| 27 |
> [2] default/linux/amd64/10.0/desktop * |
| 28 |
> |
| 29 |
> So is gcc protected somehow by the "profile"? |
| 30 |
> I think not...... |
| 31 |
> |
| 32 |
> |
| 33 |
> Still googling but not find any clear answers, |
| 34 |
> mostly cruft from years ago.... |
| 35 |
> |
| 36 |
> |
| 37 |
> James |
| 38 |
> |
| 39 |
> |
| 40 |
|
| 41 |
Short version, man make.conf for more info. buildpkg, keeps a binary of |
| 42 |
EVERYTHING installed. Now buildsyspkg only keeps binaries for system |
| 43 |
packages. If you have plenty of disk space, I would use buildpkg. If |
| 44 |
you have a lappy or are short of disk space, then buildpkg would work. |
| 45 |
Just keep in mind that some packages may not get saved. After thinking |
| 46 |
about this, I'm pretty sure I lost python once and buildsyspkg didn't |
| 47 |
keep a binary copy around. Just try to emerge something without python |
| 48 |
installed. :-( |
| 49 |
|
| 50 |
There is no list for you to keep. Portage does that. |
| 51 |
|
| 52 |
That help? |
| 53 |
|
| 54 |
Dale |
| 55 |
|
| 56 |
:-) :-) |
Archives