| 1 |
> > My unattended daily system maintenance procedure is like this: |
| 2 |
> > |
| 3 |
> > layman -S |
| 4 |
> > emerge --sync |
| 5 |
> > emerge -pvDuN world |
| 6 |
> > emerge -pv --depclean |
| 7 |
> > eclean -p distfiles |
| 8 |
> > eclean -p packages |
| 9 |
> > |
| 10 |
> > And then attended like this: |
| 11 |
> > |
| 12 |
> > |
| 13 |
> > revdep-rebuild |
| 14 |
> > etc-update |
| 15 |
> > elogv |
| 16 |
> > emerge --depclean |
| 17 |
> > eclean distfiles |
| 18 |
> > eclean packages |
| 19 |
> > |
| 20 |
> > Am I missing any good stuff? |
| 21 |
> > |
| 22 |
> > - Grant |
| 23 |
> |
| 24 |
> |
| 25 |
> I'd tweak the order of your attended run: |
| 26 |
> |
| 27 |
> emerge -DuN world |
| 28 |
> emerge @preserved-rebuild |
| 29 |
> emerge --depclean |
| 30 |
> revdep-rebuild |
| 31 |
> |
| 32 |
> |
| 33 |
> The logic is: |
| 34 |
> |
| 35 |
> Rebuild busted packages that portage already knows about |
| 36 |
> (@preserved-rebuild), then get rid of oudated packages and finally |
| 37 |
> revdep-rebuild to fix anything that --depclean broke. |
| 38 |
> |
| 39 |
> @preserved-rebuild is getting very good at what it does lately |
| 40 |
> (supported in all recent portage version including stable IIRC), as is |
| 41 |
> --depclean, so revdep-rebuild seldom finds anything to do these days. |
| 42 |
> |
| 43 |
> -- |
| 44 |
> Alan McKinnon |
| 45 |
|
| 46 |
If revdep-rebuild does everything that @preserved-rebuild does and more, |
| 47 |
why run @preserved-rebuild at all? |
| 48 |
|
| 49 |
- Grant |
Archives