git transition plan for base/user/cperciva/freebsd-update-build

[Alan Somers]

On Fri, Jan 29, 2021 at 2:21 PM Juraj Lutter <otis at freebsd.org> wrote:

>
> > On 29 Jan 2021, at 22:06, Alan Somers <asomers at freebsd.org> wrote:
> >
> > On Fri, Jan 29, 2021 at 1:28 PM Juraj Lutter <otis at freebsd.org> wrote:
> >
> >
> > > On 29 Jan 2021, at 21:12, Alan Somers <asomers at freebsd.org> wrote:
> > >
> > > What is the plan to transition the
> > > https://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/
> code?
> > > It's not really a branch of src; it's more like an independent project.
> > > Will it be getting its own repository?
> >
> > This is a good question. The other question is if it could be simplified
> somehow,
> > for use cases where users do not want/need patches and only want to
> build updates for
> > their running systems for regular maintenance.
> >
> > For users who don't need patches?  Do you mean as a substitute for the
> old:
> >
> > $ cd /usr/src
> > $ svn up
> > $ make buildworld
> > $ make buildkernel
> >
> > Or by "don't need patches", do you mean building updates based on
> tracking stable/12 instead of downloading the security advisory patches?  I
> don't think the former makes sense.  For just one system, building world
> and kernel by hand is much easier than using freebsd-update-build.
>
> Yes, I mean building updates based on tracking stable/12 (a rolling?
> release, sort of).
> For just one system, buildworld seems OK, but for more systems it may be a
> burden.
>

Yeah, that could work.  The updates might be very large, though.


>
> Have you also considered pkgbase?
>

I've never tried it.  Last I heard it still had some rough edges.  For
example, if a new package were added to the base system, pkgbase wouldn't
automatically install it.