Date: Tue, 3 Sep 2024 12:18:06 -0600 From: Alan Somers <asomers@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-hackers@freebsd.org Subject: Re: It's not Rust, it's FreeBSD (and LLVM) Message-ID: <CAOtMX2go95=RFjegzchgMTYNdZfatzGDVcavp8O6=bK9yks1bQ@mail.gmail.com> In-Reply-To: <CANCZdfrhK1iTZL5uxciqK_FGb%2Bzha_NZ15LsY42f%2B_z3KbPmJw@mail.gmail.com> References: <202409031532.483FW0If007252@critter.freebsd.dk> <CANCZdfrhK1iTZL5uxciqK_FGb%2Bzha_NZ15LsY42f%2B_z3KbPmJw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 3, 2024 at 12:10=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote: > > > > On Tue, Sep 3, 2024 at 9:32=E2=80=AFAM Poul-Henning Kamp <phk@phk.freebsd= .dk> wrote: >> >> As part of the migration, we yank LLVM out of the src. > > >> >> "pkg upgrade" also upgrade kernel and userland packages - Welcome to >> the century of the fruitbat. > > >> >> And yes, we have ports written in Rust, why do you ask? > > > pkgbase is the path forward. It is the future. We are better off putting = all our > horses behind that effort so we can make it the default install in 15.0. > > Once we have that, this whole debate becomes moot, for the most part. > Userland in rust can compete with userland in C. And with go, python, etc > for whatever does the job the best. If rust is so much better, then peopl= e > will use it, otherwise they will use the C version. How will pkgbase handle the private interface problem? 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. As long as those interfaces' consumers are all within src there's no problem, but if they move to ports then they'll need to be rebuilt everytime the libifconfig or kernel port, respectively, gets rebuilt.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2go95=RFjegzchgMTYNdZfatzGDVcavp8O6=bK9yks1bQ>