Re: Status of syspkg or similar

[Staffan Thomén <staffan%shangtai.net@localhost>]

Sad Clouds wrote:
> On Sat, 22 May 2021 17:43:31 +0900 Yuuki Enomoto<uki%e-yuuki.org@localhost>  wrote:
>
> > Hello,
> >
> > > From what I can tell the feature is somewhat unfinished/abandoned?
> > Yes. "build.sh syspkgs" can create packages. But these may remove exist
> > files/directories by install. I think, we should fix it completely
> > and/or make sysinst support this for testing.

A hybrid/staged solution might be worth considering.

I've often thought about how the not-exactly-core utilities like tmux
(but window would probably not have fallen into this category
were it still there), postfix and bind (possibly also ssh, openssl might be
too difficult to extract) _that have more alternate/newer versions in pkgsrc_
could live in their own set so I wouldn't have to install them and then just
install the pkgsrc version and be stuck with two.

That set would then be a prime target for syspkg, leaving everything else in
the sets that might have more complicated dependencies and/or were
historically part of the berkeley distribution.

I'm not too familiar with syspkg, but perhaps the pkg tools then could be
taught to upgrade them to pkgsrc if the admin wants to (hell, this might even
be there already).

.2c
Staffan

Because this is just me sprouting my musings, it's just sent to the list. It's
ok to CC me.