| 1 |
Mick wrote: |
| 2 |
> On Monday 29 Jul 2013 13:07:44 Dale wrote: |
| 3 |
>> |
| 4 |
>> |
| 5 |
>> If you set buildpkg in make.conf, you should already have a binary |
| 6 |
>> stored. Example. You do a install with buildpkg in make.conf. From |
| 7 |
>> that point on, when you do a update or new package install it stores a |
| 8 |
>> binary package for everything. Then later on if you do a update and it |
| 9 |
>> goes goofy, you can just use the -K option and it will restore the |
| 10 |
>> binary it stored without compiling the package again. |
| 11 |
>> |
| 12 |
>> I have that set here and it should do what you want in the long run. It |
| 13 |
>> just does it differently. |
| 14 |
>> |
| 15 |
>> Dale |
| 16 |
> |
| 17 |
> It's been so long since I've used this feature I forgot how binary |
| 18 |
packages |
| 19 |
> are purged. Do they stay in $PKGDIR for ever, until something like |
| 20 |
eclean |
| 21 |
> deals with them, or can you specify (where?) to only keep the last n |
| 22 |
versions? |
| 23 |
> |
| 24 |
|
| 25 |
As far as I know, eclean is the only way to clean them. It's a manual |
| 26 |
thing but I guess one could script it and do a cron job. |
| 27 |
|
| 28 |
Dale |
| 29 |
|
| 30 |
:-) :-) |
| 31 |
|
| 32 |
-- |
| 33 |
I am only responsible for what I said ... Not for what you understood or |
| 34 |
how you interpreted my words! |
Archives