Date: Sun, 12 Jul 2026 09:27:58 -0700 From: Mark Millard <marklmi@yahoo.com> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> Cc: freebsd-pkgbase <freebsd-pkgbase@freebsd.org> Subject: Re: Old /usr/bin/* files (and more) still around on modern main, long updated via pkgbase: looks like having FreeBSD-src installed and doing make check-old and the like are appropriate? Message-ID: <2826BC9C-63C4-4194-91FC-AA9D4EE290A3@yahoo.com> In-Reply-To: <865x2k390r.fsf@ltc.des.dev> References: <00b31e87-a4ee-4f04-ad74-c2b14fc9bcc5@yahoo.com> <865x2k390r.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
On Jul 12, 2026, at 01:30, Dag-Erling Smørgrav <des@FreeBSD.org> wrote: > Mark Millard <marklmi@yahoo.com> writes: >> On a upstream pkgbase system (pkgbase'd for a long time) I typed a >> command, expecting the file to not be found:. But I got a command >> from/for x86_64-unknown-freebsd15.0 . >> >> # llc --version >> LLVM (http://llvm.org/): >> LLVM version 19.1.5 >> Optimized build. > > We've never shipped llc as part of the default install, so this shows > this system was previously maintained from source using non-standard > build options. True, as I well understood but probably should have been explicit about. Also, the context was main, as is usual for me. >> That leads me to wonder what else is old that is still around. So, >> based on having the matching FreeBSD-src installed: [...] > > pkgbase does not leave old files around. These files were there before > you converted. "files were there before I converted": true. The official upstream pkgbase distribution that I used did not on its own do an equivalent of delete-old when I converted. But, thinking about it, I converted somewhat before pkgbasify became public, following other instructions, so more manual than pkgbasify. I was deliberately converting to an official, upstream distribution, not to the equivalent of my prior personal builds as well. Thus: not surprising --and my example does not necessarily match what a modern supported conversion would do for such a context via pkgbasify use. >> Did I miss some sort of documented cleanup step? > > Yes, back when you were maintaining this system from source, you should > have run `make delete-old` and `make delete-old-libs` regularly. I always did after I installed my personal build (delete-old) or, possibly, somewhat later (delete-old-libs). Nothing that I wrote indicated otherwise. You jumped to a false conclusion about my not following standard procedures for such in my historical style of operation for my type of context that I used before my conversion. My conversion deliberately involved an official, upstream pkgbase distribution, not my own build. So: no longer an analogous context for my boot environment. Following the instructions was a deliberate experiment at the time. Had I done it somewhat later, it would have been a pkgbasify experiment instead. As stands, at no point before my conversion completed would make delete-old have removed the files that I reported. If an analogous pkgbasify conversion was done these days, I do not know if it would. > You > also shouldn't have converted to pkgbase using packages built with > different options than what you'd been using previously. No: I no longer boot a personal environment by default. I have a chroot directory tree I now use for my personal world when I want to use such. I have an additional personal kernel that I can boot as well. (I have at least one configuration that I use that requires such.) You have jumped to conclusions about what I was attempting to establish as the new type of context by doing a conversion to pkgbase use. > You should > have simply done a last buildworld + buildkernel with the same options, > then run `make update-packages` and installed the result. No, not for what I wanted to establish as a new type of context. As I have /usr/src/ being from FreeBSD-src and other /usr/*src*/ trees for other contexts, I just cleaned things up with make delete-old from the pkgbase /usr/src/ tree. (check-old had reported no libraries for delete-old-libs to deal with.) Note: My personal kernel and world builds still are not based on building a pkgbase repository and they still use non-standard build options and the personal kernel has some of my own patches for specific issues. For example, for aarch64, I have to use my kernel for an 8 GiByte RPi4 booted via EDK2 to operate correctly/reliably when the 3 GiByte limitation is disabled in EDK2. > DES > -- > Dag-Erling Smørgrav - des@FreeBSD.org Overall: It appears that anyone converting from a non-defaul personal build of the system to an official, upstream pkgbase distribution may have similar issues to what I had and may need to clean out what became extra/old files. === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2826BC9C-63C4-4194-91FC-AA9D4EE290A3>