Re: It's not Rust, it's FreeBSD (and LLVM)

 Hi Alan,

On Tue, 3 Sep 2024 14:19:02 -0600
Alan Somers <asomers@freebsd.org> wrote:

> On Tue, Sep 3, 2024 at 1:50?PM Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> >
> > --------
> > Alan Somers writes:
> >
> > > For example, libifconfig and the /dev/cam/ctl ioctls are both unstable.
> > > A port that uses one of those and is built for FreeBSD 14.0 won't
> > > necessarily work for 14.1.
> >
> > Isn't that also a problem today ?
> >
> > What difference does it make that src is distributed as a package ?
> 
> Not "a package" but "many packages".  The pkgbase concept builds a
> separate package for almost every dir under lib, bin, sbin, usr.bin,
> and usr.sbin.

 Not really true, pkgbase creates a packages for each tools or set of
tools (when it make sense).

> So the problem will be that libifconfig and its
> consumers will be distributed separately, whereas they are currently
> distributed together.
> -Alan
> 

 libifconfig is an internal lib so I'm not sure this is the best
example here (and it's internal lib because it's not stable and I don't
think that you can use it in a port right now unless the port
uses /usr/obj/ from the host or can build the lib from /usr/src, both
solution will create problems).
 But anyway, this isn't a problem to update multiple packages at the
same time, yes there will probably be a time during the update where
the lib is updated and the binary isn't yet (or the other way around)
but that's the same with any ports that depends on a lib present in
another ports.

 Also for sources there is only two packages, FreeBSD-src-sys (for the
kernel) and FreeBSD-src (for anything else).

 I'm not sure that I understand the problem you're trying to describe.

 Cheers,

-- 
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>