|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
building m:tier-like -stable package updates
Hello daemonforums.org, hello fellow OpenBSD users!
I am currently in the process of replacing some linux-bases machines with OpenBSD. On some I can neither run -current, compile ports directly, or use m:tiers service. This leaves me with building my own -stable packages. I am in the process of familiarizing myself with dpb and proot and able to build updates for a subset of packages I provide . However, I wonder how to keep track of which ports need updating and how to build different subsets of packages for different hosts in a semi-automated fashion. One way I could think about is to build the whole tree (is that even possible?) and then just sequentially pull cvs and rebuild, but man dpb even talks about Code:
dpb -R In the end i am looking for a m:tier-like solution i can run in an closed environment. I would be grateful for any hints or tips, thanks. |
|
|||
Provided you're diligent in keeping your -stable ports tree up to date with CVS, are you looking for something like PORTSDIR/infrastructure/bin/pkg_outdated?
|
|
|||
pkg_outdated compares to installed ports. So your build machine would need all the ports you use to be installed.
My production systems use few enough ports that I just monitor cvs for changes and rebuild when something I use or depend on changes. Use proot(1) to keep the ports builds isolated from the build machine's installed packages. |
|
|||
Thanks for your replies.
Quote:
I also wonder if dpb is able to use pkg_add to fetch build-dependencies - FETCH_PACKAGES=yes in mk.conf seems to have no effect. Thanks, but the build-machine itself will not have any packages installed. |
|
|||
Quote:
I just run 'cvs -qn up' in /etc/daily.local and manually look at it. I suppose you could script a build trigger from there but tracking all the transient dependencies might be tedious. dpb won't build a version that is already built, so you could probably so just 'cvs up' and run dpb every day. Let 'pkg_add -n' on the clients tell you when there is a new package. I don't do this only because I didn't want to script cleaning up previous versions of packages. I just blow everything away and rebuild. I sign, too so need to enter a passphrase anyway. |
|
|||
I did, and actualy tried to use pkg_add in the chroot which works. Seems like dpb just does not support FETCH_PACKAGES at the moment (tweak_args in infrastructure/lib/DPB/Job/Port.pm seems to be responsible for this)
|
|
|||
FETCH_PACKAGES=Yes works with or without PKG_PATH.
When specified manually while building a port, it works (for example): Code:
make FETCH_PACKAGES=Yes install This seems like a bug, since 'man ports' implies that FETCH_PACKAGES should work in those contexts. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
OpenBSD Binary updates for -stable are in development | jggimi | News | 2 | 13th September 2016 01:57 AM |
tracking -stable compiling only updates | Funkygoby | OpenBSD Installation and Upgrading | 3 | 16th January 2016 08:31 PM |
M:tier Updates - Positive Experience | shep | OpenBSD General | 1 | 16th March 2014 03:13 PM |
*** Error code 1 building OpenBSD 5.1-stable from source | comet--berkeley | OpenBSD Installation and Upgrading | 12 | 19th May 2012 02:18 AM |
stable branch - ports security updates | albator | OpenBSD Packages and Ports | 22 | 5th September 2011 01:58 AM |