Re: port binary updates

From: Sysadmin Lists <sysadmin.lists_at_mailfence.com>
Date: Wed, 08 Jun 2022 19:13:49 UTC
You might be right. Can't check now but I thought my servers were running plain
poudriere, but might still be on -devel (I switched to -devel when that feature first
dropped but thought I switched back).

> ----------------------------------------
> From: Dave Cottlehuber <dch@skunkwerks.at>
> Sent: Wed Jun 08 21:04:23 CEST 2022
> To: Sysadmin Lists <sysadmin.lists@mailfence.com>
> Subject: Re: port binary updates
> 
> 
> Did you check the code? AFAICT it’s not present in  default.
> 
> Dave
> 
> On Wed, 8 Jun 2022, at 21:01, Sysadmin Lists wrote:
> >> ----------------------------------------
> >> From: Arthur Chance <freebsd@qeng-ho.org>
> >> Sent: Tue Jun 07 18:06:43 CEST 2022
> >> To: Dave Cottlehuber <dch@skunkwerks.at>, <questions@freebsd.org>
> >> Subject: Re: port binary updates
> >> 
> >> 
> >> On 07/06/2022 17:03, Dave Cottlehuber wrote:
> >> > On Tue, 7 Jun 2022, at 15:21, Arthur Chance wrote:
> >> >> On 07/06/2022 16:08, Dave Cottlehuber wrote:
> >> >>> On Tue, 7 Jun 2022, at 11:32, Arthur Chance wrote:
> >> >>>> In theory it's supposed to be possible to use poudriere hooks to fetch
> >> >>>> prebuilt packages from the FreeBSD repositories, but I've never found it
> >> >>>> how. If anyone has ideas/incantations on this they'd be very welcome.
> >> >>>
> >> >>> I've not tested this, but it should be correct, extracted from our
> >> >>> ansible stuff.
> >> >>>
> >> >>> - poudriere-devel poudriere-devel-3.3.99.20211130
> >> >>>
> >> >>> # ansible managed
> >> >>> # ... snip
> >> >>> # seed packages from pkg.FreeBSD.org
> >> >>> # pick either latest or quarterly as you like
> >> >>> PACKAGE_FETCH_BRANCH="latest"
> >> >>> # allow or deny, pick one
> >> >>> # PACKAGE_FETCH_WHITELIST="gcc* rust* llvm* mono* cargo cmake openjdk*"
> >> >>> # PACKAGE_FETCH_BLACKLIST="zig* collectd* foundationdb* erlfdb"
> >> >>
> >> >> I'm probably being a bit slow, but where do the above lines go? [I'm
> >> >> running poudriere rather than poudriere-devel if that makes a difference.]
> >> > 
> >> > Woops, that is somewhat relevant:
> >> > 
> >> > /usr/local/etc/poudriere.conf
> >> > 
> >> > AFAICT this is not in ports-mgmt/poudriere yet, only in the -devel flavour.
> >> 
> >> Thanks. I feel a switch to the -devel version coming on. Building llvm
> >> on my machine wastes rather a lot of time and bottlenecks many other big
> >> builds.
> >
> > There's no need to switch to -devel. That feature was added to 
> > poudriere many months ago.
> > One thing to note: if you run a poudriere jail update before building 
> > ports, it rebuilds
> > all of them. Only update the jails when you know an update exists. 
> > That, plus the prefetch
> > option makes package upgrades very simple. And when you feel brave 
> > enough you can start
> > mixing binaries and ports, using the locking feature and multiple repos.
> >
> >
> >
> > -- 
> > Sent with https://mailfence.com  
> > Secure and private email
> 
> -- 
> —
>   Dave Cottlehuber
>   signal:+436767224478
>   webrtc: https://cabal.whereby.com/dch
>   company: https://skunkwerks.at/
>   Managing Director
>   SkunkWerks, GmbH
>   ATU70126204
>   Firmenbuch 410811i


-- 
Sent with https://mailfence.com  
Secure and private email