| 1 |
On Mon 15 August 2011 11:33:02 Paul Hartman did opine thusly: |
| 2 |
> On Mon, Aug 15, 2011 at 3:27 AM, Alan McKinnon |
| 3 |
<alan.mckinnon@×××××.com> wrote: |
| 4 |
> > That caught me out a few times too. I put these commands into a |
| 5 |
> > bash alias: |
| 6 |
> > |
| 7 |
> > emerge --sync |
| 8 |
> > layman -S |
| 9 |
> > eix-update |
| 10 |
> > |
| 11 |
> > and use that to sync portage. That way I don't leave steps out. |
| 12 |
> |
| 13 |
> Congratulations, you reinvented the "eix-sync" command. :) |
| 14 |
|
| 15 |
You caught me out :-) |
| 16 |
|
| 17 |
There was a reason (a good one) why I did that several years ago, but |
| 18 |
for the life of me I can't think what it was. |
| 19 |
|
| 20 |
"several years ago" should be my clue to assume the reason is no |
| 21 |
longer valid .... |
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
> |
| 26 |
> You can put a list of layman overlays to be synced in |
| 27 |
> /etc/eix-sync.conf or a line simply containing an asterisk (*) to |
| 28 |
> sync 'em all. |
| 29 |
> |
| 30 |
> You can also put arbitrary post-sync commands in there, like if you |
| 31 |
> have an overlay that needs an egencache update or if you have some |
| 32 |
> local patches that you always apply to an ebuild from an overlay. (I |
| 33 |
> think most of that sort of thing is not necessary anymore because |
| 34 |
> of other, better ways of handling that.) |
| 35 |
-- |
| 36 |
alan dot mckinnon at gmail dot com |
Archives