One of the (if not THE) thing I found appealing about FreeBSD was not having to think about or be concerned with that. You install FreeBSD, you get what you need to run (ports/packages) on FreeBSD.packages installed from ports might depend on packages from the base system
On 8/7/2025 10:17 PM, Colin Percival wrote:
On 8/7/25 18:20, vermaden wrote:OK, Colin Percival just announced 15.0-PRERELEASE - yet the PKGBASE concept - besides 'kinda working' - does not holds to the POLA principle at all - and if anyone will chose to use PKGBASE instead of 'classic' install the 'pkg delete -af' will not only delete all the third party packages but will also WIPE almost ENTIRE BASE SYSTEM of FreeBSD ... this is not unacceptable to say the least.POLA is inherently subjective; what astonishes one person might be exactly what another person expects. In this particular case, while someone might indeed be astonished that "forcibly delete everything" deletes everything,someone else could well be astonished if "pkg delete -f clang" doesn't in fact delete clang.My 'vote' here does not changed. Lets keep pkg(8) for third party packages with: - /etc/pkg - /usr/local/etc/pkg - /var/db/pkg Lets have pkgbase(8) for FreeBSD Base System PKGBASE with: - /etc/pkgbase - /usr/local/etc/pkgbase - /var/db/pkgbaseI would like this idea, except for one wrinkle: I don't think it would work. In particular, packages installed from ports might depend on packages from the base system, so having a single tool which knows about both is necessary.
smime.p7s
Description: S/MIME Cryptographic Signature
