Date: Wed, 4 Sep 2024 07:56:09 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Warner Losh <imp@bsdimp.com> Cc: Alan Somers <asomers@freebsd.org>, Poul-Henning Kamp <phk@phk.freebsd.dk>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: It's not Rust, it's FreeBSD (and LLVM) Message-ID: <20240904075609.a07ee81552928a0ecea273cd@bidouilliste.com> In-Reply-To: <CANCZdfrMePQKQ47_wh0CL54k=bhgQwU_k3z4RANmPWCfBm7h=w@mail.gmail.com> References: <202409031532.483FW0If007252@critter.freebsd.dk> <CANCZdfrhK1iTZL5uxciqK_FGb%2Bzha_NZ15LsY42f%2B_z3KbPmJw@mail.gmail.com> <CAOtMX2go95=RFjegzchgMTYNdZfatzGDVcavp8O6=bK9yks1bQ@mail.gmail.com> <202409031950.483JoBuh009465@critter.freebsd.dk> <CAOtMX2jwu9bUDgM=jxtP5t794VUPjNx3GtrVgYqvGcSiZqHwVQ@mail.gmail.com> <CANCZdfrJ149NguCYMuZs8M7cswQGkLnRYqsfND4Jpc7yajU_Jg@mail.gmail.com> <CAOtMX2j%2BT3h9mg8a0AcYMbg2%2BWQFN14NhaQFs%2BjM-3hAmNBsBg@mail.gmail.com> <CANCZdfrMePQKQ47_wh0CL54k=bhgQwU_k3z4RANmPWCfBm7h=w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Warner, On Tue, 3 Sep 2024 17:07:53 -0600 Warner Losh <imp@bsdimp.com> wrote: > On Tue, Sep 3, 2024 at 2:40?PM Alan Somers <asomers@freebsd.org> wrote: >=20 > > On Tue, Sep 3, 2024 at 2:21?PM Warner Losh <imp@bsdimp.com> wrote: > > > > > > > > > > > > On Tue, Sep 3, 2024, 2:19?PM 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. So the problem will be that libifconfig and its > > >> consumers will be distributed separately, whereas they are currently > > >> distributed together. > > > > > > > > > Won't versions and dependencies solve this? They aren't tied to a ker= nel > > version since its a stable ABI. > > > > > > Warnrr > > >> > > >> -Alan > > > > Aren't you the one who just said that the ABI will need to become > > stable? Or did you only mean that about the /dev/cam/ctl ioctls? For > > private libs, the easiest thing would be if pkgbase could put libs and > > their consumers into the same package. But that might not always be > > possible. > > >=20 > Generally, you're supposed to update all the packages in the system, which > would keep > things from getting cross threaded. >=20 > However, I had thought that 'pkg upgrade libfoo' would upgrade all things > that depended > on libfoo. If the lib is properly versioned it will, pkg records any libs that the package depends on in the shlibs_required table and any libs that the package provides in shlibs_provided. So if the package libfoo provides libfoo.so.9 and it's updated to provides libfoo.so.10 any packages that now requires the .10 version will be updated. > However, it doesn't go 'up' the dependency tree, but just 'down' > for things that libfoo > depends upon. It's one of the fragile things about pkg today used with > ports (though often > it's totally fine, since the ABIs are usually stable)... Not sure I follow here. > I'm not familiar enough with the ctl ioctl to state definitively... > However, it appears, at first blush, > to be fairly stable though. >=20 > Warner --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240904075609.a07ee81552928a0ecea273cd>