Re: FreeBSD-set-src package is marked as vital?

pkg would autoremove the FreeBSD-set-src package or it's dependencies if it isn't marked as vital?

i can think of two reasons as to why it shouldn't be marked as vital, first is that anyone who has deliberately git cloned the base src tree and deliberately modified it wouldn't want their modifications to get overwritten anytime and the FreeBSD-src and related packages obviously overwrite any change anytime they(the packages of FreeBSD-set-src) get upgraded
second is that not everyone needs or wants a copy of src tree on their system by default which i assume they will get when they use pkgbase to install freebsd since it's marked as vital
-------- Original Message --------
On Friday, 10/17/25 at 11:48 Lexi Winter <ivy@freebsd.org> wrote:
polyduekes@proton.me wrote in <PVQdhBX2BCzNWF3IiOwspzh178rPQoj8flgVfbYQJzba9AfvuuFRKqYbj1R3gvOc8TjCCx0N5xTSt0jBVLXDCTZr0s_uGxWHD7-i7bLZuKI=@proton.me>:
> i would like to report it but I wanted to gather opinions on the
> matter of FreeBSD-set-src being marked as vital first

all sets are marked as vital to avoid issues with pkg autoremove, and i
don't see any particular reason to change this for set-src specifically.

the issue when attempting to remove a package which is part of a set is
already tracked here: https://github.com/freebsd/pkg/issues/2517.  this
is supposed to be fixed for 15.0-RELEASE, although i'm not sure if
anyone is actually working on it.  in any case, this affects all sets,
not just set-src, so removing the vital flag from set-src wouldn't fix
the problem.