Date: Sat, 24 Mar 2018 14:26:29 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 226893] freebsd-update supporting explicit patch-level for fetch+upgrade Message-ID: <bug-226893-8-YYMrc94kj3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-226893-8@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226893 --- Comment #1 from Derek <482254ac@razorfever.net> --- It was expressed that "it would be nice if" we could list the available patch levels, for example, and by extension if we can specify that patch level by number, instead of existing tag hash. 1. Without updates to the freebsd-update server portion, the only way that I can see this being feasible is to download all the available tags for a release, and then pull down their manifests and see if there's a file that can be downloaded (e.g. whatever freebsd-version is sourcing), and parsed. I feel like this is needlessly onerous. 2. A different method, would be in addition to latest.ssl, we also support all.ssl, which is the concatenation of all of the latest.ssl released for a particular release/architecture. This will require changes to the freebsd-update server portion, and will need support added retroactively for previous supported releases. It would be trivial to modify to the freebsd-update client to support this file instead (or in addition to). 3. A third, most hacky, option is just to specify the tag hash on the command line, and put the onus on the user to research the tag they wish to install. There's likely other approaches, but I'm partial to #2. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226893-8-YYMrc94kj3>