| 1 |
Thanasis <thanasis@××××××××××.org> wrote: |
| 2 |
> on 07/10/2013 09:38 AM Martin Vaeth wrote the following: |
| 3 |
>> |
| 4 |
>> This has nothing to do with the necessity to call "eix-remote add" |
| 5 |
>> after eix-sync |
| 6 |
|
| 7 |
With eix-0.29.0 which just entered the tree, eix-sync will |
| 8 |
by default do this for you, so you usually do not need to |
| 9 |
care about. |
| 10 |
|
| 11 |
> My goal is to be able to query both local and remote data with one |
| 12 |
> command. |
| 13 |
|
| 14 |
Either you use eix -R ... (or eix -Z ...) or, alternatively, |
| 15 |
you set REMOTE_DEFAULT=1 (or -2) to avoid typing -R/-Z. |
| 16 |
(You have to type -R/-Z then if you want *only* a local query). |
| 17 |
|
| 18 |
> what would the sequence of commands be for updating |
| 19 |
|
| 20 |
With >=eix-0.29.0, if you use eix-sync, this will completely |
| 21 |
care about updating the local data. |
| 22 |
|
| 23 |
If you call eix-update manually (e.g. after changing some |
| 24 |
local overlay manually) you should call afterwards |
| 25 |
eix-remote add1 (and/or eix-remote add2, depending on whether |
| 26 |
you use -R or -Z, i.e. depending which remote data you use). |
| 27 |
|
| 28 |
For updating the remote data you just use as usual |
| 29 |
eix-remote update1 (and/or eix-remote update2), |
| 30 |
|
| 31 |
If you want to do the latter automatically with every eix-sync, |
| 32 |
put e.g. the following lines into your /etc/eix-sync.conf: |
| 33 |
|
| 34 |
@StatusInfo Downloading remote1 |
| 35 |
@eix-remote fetch1 |
| 36 |
|
| 37 |
(Of course, you can replace 1 by 2 and/or add corresponding |
| 38 |
lines for 2 to fetch the alternative remote data). |
| 39 |
|
| 40 |
(In /etc/eix-sync.conf it suffices to call "eix-remote fetch" |
| 41 |
because the "eix-remote add" is called automatically |
| 42 |
after the call of eix-update). |
Archives