Re: Building Latest links etc.
On Fri, 17 Jul 2015 16:04:02 +0200 Marko Cupać marko.cu...@mimar.rs wrote: If you need to maintain custom packages for more than 5 systems then poudriere is the way to go: https://www.freebsd.org/doc/handbook/ports-poudriere.html I have also written 'works for me' detailed howto (in Sebian though): https://www.mimar.rs/sysadmin/2015/poudriere-na-freebsd-10-1 I've used poudriere, but it seems heavyweight when all I am doing is building one set of packages for one architecture. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Building Latest links etc.
On Fri, 17 Jul 2015 15:48:39 +0200 Patrick Hess patrickh...@gmx.net wrote: Bob Eager wrote: 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? Is there a particular reason why you want to use portmaster instead of just running pkg upgrade? Portmaster might be a great tool for building your packages, but when it comes to installing or upgrading these packages on another machine, I'd stick with pkg(8). Good point. I'll try that out on a test machine. After all, the package server is already a repo. I guess it was because the portmaster man page talks about it. I wonder if the whole idea is cruft left over from pre-pkg days. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Building Latest links etc.
On Fri, 17 Jul 2015 15:11:55 +0100 Matthew Seaman m.sea...@infracaninophile.co.uk wrote: 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. Good point. Of course...I already have that repository, all set up, by definition. That's how I distributed the packages in the first place! 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. poudriere is great (and I have used it) for cross-platform and cross-release stuff. With a single release, 10 systems to update, all the same, it seems more than I need. All I seem to need with portmaster is: portmaster -a pkg repo after all.. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Building Latest links etc.
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
Re: Building Latest links etc.
On Fri, 17 Jul 2015 14:15:12 +0100 Bob Eager r...@tavi.co.uk 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? Thanks If you need to maintain custom packages for more than 5 systems then poudriere is the way to go: https://www.freebsd.org/doc/handbook/ports-poudriere.html I have also written 'works for me' detailed howto (in Sebian though): https://www.mimar.rs/sysadmin/2015/poudriere-na-freebsd-10-1 Regards, -- Marko Cupać https://www.mimar.rs/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Building Latest links etc.
Bob Eager wrote: 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? Is there a particular reason why you want to use portmaster instead of just running pkg upgrade? Portmaster might be a great tool for building your packages, but when it comes to installing or upgrading these packages on another machine, I'd stick with pkg(8). Patrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Building Latest links etc.
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? Thanks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
