| 1 |
Michael, |
| 2 |
|
| 3 |
On Saturday, 2021-01-30 10:48:20 +0000, you wrote: |
| 4 |
|
| 5 |
> On Saturday, 30 January 2021 09:37:57 GMT Alan Grimes wrote: |
| 6 |
> > ... |
| 7 |
> > I mean I always update my portage first thing after sync, because that's |
| 8 |
> > what you do, RIIIIIGHT???? |
| 9 |
> |
| 10 |
> Not RIIIIIGHT. |
| 11 |
> |
| 12 |
> I let portage decide when it needs to update itself, after it has decided |
| 13 |
> which of its dependencies it may need to update first. |
| 14 |
|
| 15 |
Since I've installed Gentoo more than a year back I have a small script |
| 16 |
in "/etc/portage/postsync.d/" which just contains |
| 17 |
|
| 18 |
#! /bin/bash |
| 19 |
emerge --ask --changed-deps --changed-use --deep --newuse --oneshot \ |
| 20 |
--update --with-bdeps=y sys-apps/portage |
| 21 |
|
| 22 |
I'm not sure where I got that from, I thought it was in the Gentoo Hand- |
| 23 |
book, but looking there just now I didn't find anything like that. May- |
| 24 |
be I invented that myself. |
| 25 |
|
| 26 |
Am I interpreting you correctly that such a postsync hook is never nec- |
| 27 |
essary, that is, that the "portage" package itself is always a built-in |
| 28 |
build dependency for every other package? |
| 29 |
|
| 30 |
Sincerely, |
| 31 |
Rainer |
Archives