On 2015/07/17 14:15, Bob Eager wrote: > This is the scenario. I build all packages locally (a number have > special configs). This is done on one machine, which is then the > repository for 'pkg install'. > > So far so good. > > I now want to update the ports. I see how to do this using portmaster, > and how to generate packages on the package server. > > But...how do I use portmaster on the 'slave' machines, using the > packages I built? I can ask it to use a local directory, and NFS mount > the main package directory on the package server. But portmaster > requires the Latest directory, symlinks, etc. My manual build didn't > add those originally. > > Is there an easy way of building all the symlinks required by > portmaster? I can see how to regenerate Latest, but portmaster asks for > other stuff according to the manual page. I know portmaster -g will do > this but that won't do the existing packages. > > Is there a script somewhere, or am I over complicating things?
You don't need to use portmaster on the slave machines. Just create a
repository from the packages you've built on your primary machine --
which is basically done by runnig 'pkg repo' in the directory where
you've put all the pkg tarballs. Export that directory somehow --
either via a webserver or by NFS mounting it on the clients or some
other way. Set up a repo.conf on your clients so they will use that
repo, and then use pkg(8) to install the packages on your client machines.
Even better: rather than using portmaster, try poudriere instead, which
will help you automate a large chunk of that -- it will build all the
packages which are out of date or otherwise need refreshing and
automatically add them to your repo with just one command.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
