On Wed, Jan 31 2018, Canek Peláez Valdés wrote:
> On Wed, Jan 31, 2018 at 1:29 PM, allan gottlieb <gottl...@nyu.edu> wrote:
> [snip]
>> I have two questions, one trivial, one hopefully easy.
>>
>> 1. (trivial) In your recipe did you mean "rsync", not "sync"?
>
> I sync ("emerge --sync") only one machine, and then I rsync from there to
> my other computers. After the rsync is done, you need to do "emerge
> --metadata" in the recipient machine (--sync does that for you
> automatically).
So sync referred to an emerge command and when you copied files from
machine to machine you used rsync. Thanks.
>
>> 2. I have a number of quickpkgs built. Is it needed that
>> they all be updated and some removed or can I just do
>> the following command
>>
>> rsync -Pvase ssh machine1:/var/portage/packages/www-client \
>> /var/portage/packages
>>
>> Notes: I use /var not /usr for portage
>> machine2 has no dir /var/portage/packages/www-client
>
> I honestly don't know. There is a /usr/portage/packages/Packages with a lot
> of meta information, and I'm not 100% sure whether is absolutely required.
> Then again, creating binary packages is so fast that I usually delete
> /usr/portage/packages after updating my non-compiling machines. I know of
> people who maintain a large repository of binary packages (they can be
> built automatically with FEATURES="buildpkg" in make.conf), but I just
> create them when needed.
I have FEATURES="buildsyspkg" on all machines for safety.
It has worked in the sense that I have never needed to use
the resulting packages.
But I see your point that /var/portage/packages/Packages
may need to be updated on the target machine so it is probably
best to do your rsync of all of /var/portage/packages
>
> Regards.
> --
> Dr. Canek Peláez Valdés
thanks,
allan
