Conflict hell after freebsd-update

[Sunray]

Based upon bsdinstall/scripts/auto#L208-L218:

if [ ! -f $BSDINSTALL_DISTDIR/MANIFEST ]; then
    PKGBASE=yes
else
    bsddialog --backtitle "$OSNAME Installer" --title "Select Installation Type" \
        --yes-label "Distribution Sets" --no-label "Packages (Tech Preview)" --yesno \
        $PKGBASE_DEFAULT_BUTTON \
        "Would you like to install the base system using traditional distribution sets or packages (technology preview)?" 0 0
    if [ $? -eq 1 ]; then
        PKGBASE=yes
    fi
fi

the term actually used is Packages (Tech Preview). On 14.2|3-RELEASE and 14-STABLE pkgbase was "experimental".

I believe whether or not Packages (Tech Preview) is presented as the default option, depends on what image you are installing FreeBSD15.0-RELEASE from; AFAIK, if I'm reading this correctly, when both options are available and a MANIFEST is present then the default option is "distribution sets". IIRC a minimal (smallest?) memstick or ISO image does only offer the option of installing a packaged base; there simply isn't room for both options when space is at a minimum.


This has been discussed rather fiercly on the MLs. The fact remains that, although this is in accordance to the documented behaviour of pkg-delete(8), in the era of pre-base packages this was often used to "get rid" of any non-base stuff, that is: packages from the ports tree, and have a clearly defined state with only the base install. Some work/ideas seem to be in the making where it is easy to not affect base packges when issueing such a rigorous pkg-delete or pkg-remove command; I'm not aware of the current status of these developments.

Thanks for the clarification. Yes "Packages (Tech Preview)" is the correct term - my previous wording was based on my memory of the installer.

I really appreciated that packages were separated from the base system in the past. Hopefully, this can be achieved again with a flag or similar option in pkg, allowing users to either include or exclude base packages as needed.

 

[Sunray]

Regardless if pkgbase or not, or 3rd party packages, it's not a good idea to pkg-delete(8) -y, --yes Assume yes when asked for confirmation before package deletion. without checking what packages are removed.

Sometimes this is what you want, at least in the past, to get a clean base system. The fact that is now removes the kernel is absolute madness.

 

[Emrion]

My installation was actually FreeBSD 12 initially and I've been upgrading it. I decided to run pkgbasify yes so that is my fault.

However, I did a fresh installation right now and pkgbase (Experimental Tech) was the default selected option in the installer. Weird to have a experimental feature selected by default. I chose freebsd-update of course.

Well, it's a matter of choice. That said, it's not surprising because it is said that freebsd-update will be deprecated and, in the future, you will have nothing else than pkgbase. The future in question might be 16.0-RELEASE.

My main point was: this thead isn't about pkgbase. Don't mix things.

 

[Sunray]

Well, it's a matter of choice. That said, it's not surprising because it is said that freebsd-update will be deprecated and, in the future, you will have nothing else than pkgbase. The future in question might be 16.0-RELEASE.

My main point was: this thead isn't about pkgbase. Don't mix things.

I suspected pkgbasify.lua since it overwrites the user repro conf file. But others in this thread reported the same issue with freebsd-update so it can't be that.