Page MenuHomeFreeBSD

pkgbase: use weekly by default
AcceptedPublic

Authored by bapt on Fri, Jan 9, 8:10 AM.
Tags
None
Referenced Files
F142084331: D54610.diff
Thu, Jan 15, 9:44 PM
Unknown Object (File)
Wed, Jan 14, 4:55 AM
Unknown Object (File)
Sat, Jan 10, 8:50 AM
Unknown Object (File)
Fri, Jan 9, 7:24 PM
Unknown Object (File)
Fri, Jan 9, 3:42 PM
Unknown Object (File)
Fri, Jan 9, 3:16 PM
Unknown Object (File)
Fri, Jan 9, 2:09 PM
Subscribers

Details

Reviewers
bdrewery
manu
Group Reviewers
pkgbase
Summary

On stable, prefer the weekly repository over the latest repository,
which is a saner pace of updates for most people and aligned with the
kmods which are themselves always build on the weekly snapshots of
pkgbase.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 69741
Build 66624: arc lint + arc unit

Event Timeline

bapt requested review of this revision.Fri, Jan 9, 8:10 AM
This revision is now accepted and ready to land.Fri, Jan 9, 8:20 AM

This will also affect -CURRENT no ? (but it's also better to use weekly by default here)

yes it will also affect current

this means people won't get security updates for up to a week. is that acceptable?

I think it is, if you run, stable or current, you are supposed to know what you are doing.

okay, but even if you know what you're doing, you still aren't going to get security updates :-)

is the expectation that people would do a one-off build to fix the security issue then go back to using the pkg.f.o builds?

let's say I see a security issue, which affects my use case, I would switch temporary on latest and switch back on weekly a couple of days later.
We can also align the EN/SA release date on the weekly or the other way around, so the next weekly happen few hours after the EN/SA are issued

okay, i don't object to this but i feel like (at some point in the future) we could have a better solution somehow.