Thanasis <[email protected]> wrote: > on 07/10/2013 09:38 AM Martin Vaeth wrote the following: >> >> This has nothing to do with the necessity to call "eix-remote add" >> after eix-sync
With eix-0.29.0 which just entered the tree, eix-sync will by default do this for you, so you usually do not need to care about. > My goal is to be able to query both local and remote data with one > command. Either you use eix -R ... (or eix -Z ...) or, alternatively, you set REMOTE_DEFAULT=1 (or -2) to avoid typing -R/-Z. (You have to type -R/-Z then if you want *only* a local query). > what would the sequence of commands be for updating With >=eix-0.29.0, if you use eix-sync, this will completely care about updating the local data. If you call eix-update manually (e.g. after changing some local overlay manually) you should call afterwards eix-remote add1 (and/or eix-remote add2, depending on whether you use -R or -Z, i.e. depending which remote data you use). For updating the remote data you just use as usual eix-remote update1 (and/or eix-remote update2), If you want to do the latter automatically with every eix-sync, put e.g. the following lines into your /etc/eix-sync.conf: @StatusInfo Downloading remote1 @eix-remote fetch1 (Of course, you can replace 1 by 2 and/or add corresponding lines for 2 to fetch the alternative remote data). (In /etc/eix-sync.conf it suffices to call "eix-remote fetch" because the "eix-remote add" is called automatically after the call of eix-update).
