• FreeBSD-set-src package is marked as vital?

    From polyduekes@polyduekes@proton.me to muc.lists.freebsd.stable on Thu Oct 16 18:20:23 2025
    From Newsgroup: muc.lists.freebsd.stable

    i noticed that i have FreeBSD-src and FreeBSD-src-sys installed even though i never installed them, when i tried to remove them with pkg remove FreeBSD-src-sys i got
    pkg remove FreeBSD-src-sys-15.0.b1.20251015211959
    Cannot solve problem using SAT solver, trying another plan
    Cannot solve problem using SAT solver, trying another plan
    Checking integrity... done (0 conflicting)
    1 packages requested for removal: 0 locked, 1 missing
    the "1 missing" really confused me, if it wasn't for a helpful guy from the community i wouldn't have figured out that the issue was that "FreeBSD-set-src" is marked as vital, so i think it would really helpful if it is possible that pkg can tell that instead of saying "1 missing"
    another thing that confuses me is whether or not FreeBSD-set-src is marked as vital on purpose?
    Thanks, Polyduekes
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polyduekes@polyduekes@proton.me to muc.lists.freebsd.stable on Fri Oct 17 05:21:30 2025
    From Newsgroup: muc.lists.freebsd.stable

    --b1=_HpWCAuFtH7xV16aRW1lio0mQsdtTromdHLltjOmkmw
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: base64

    aSB3b3VsZCBsaWtlIHRvIHJlcG9ydCBpdCBidXQgSSB3YW50ZWQgdG8gZ2F0aGVyIG9waW5pb25z IG9uIHRoZSBtYXR0ZXIgb2YgRnJlZUJTRC1zZXQtc3JjIGJlaW5nIG1hcmtlZCBhcyB2aXRhbCBm aXJzdAotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tCk9uIEZyaWRheSwgMTAvMTcv MjUgYXQgMDY6NDAgR3JhaGFtIFBlcnJpbiA8Z3JhaGFtcGVycmluQGdtYWlsLmNvbT4gd3JvdGU6 Cgo+IChSZWR1Y2VkIHRvIHRoZSBtYXhpbXVtIG9mIHR3byBsaXN0cykKPgo+IE9uIDE2LzEwLzIw MjUgMTk6MjAsIHBvbHlkdWVrZXNAcHJvdG9uLm1lIHdyb3RlOgo+Cj4+IOKApiB0aGUgIjEgbWlz c2luZyIgcmVhbGx5IGNvbmZ1c2VkIG1lLCBpZiBpdCB3YXNuJ3QgZm9yIGEgaGVscGZ1bCBndXkg ZnJvbSB0aGUgY29tbXVuaXR5IGkgd291bGRuJ3QgaGF2ZSBmaWd1cmVkIG91dCB0aGF0IHRoZSBp c3N1ZSB3YXMgdGhhdCAiRnJlZUJTRC1zZXQtc3JjIiBpcyBtYXJrZWQgYXMgdml0YWwsIHNvIGkg dGhpbmsgaXQgd291bGQgcmVhbGx5IGhlbHBmdWwgaWYgaXQgaXMgcG9zc2libGUgdGhhdCBwa2cg Y2FuIHRlbGwgdGhhdCBpbnN0ZWFkIG9mIHNheWluZyAiMSBtaXNzaW5nIgo+Cj4gKzEKPgo+IFs8 aHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9hcmNoaXZlcy9mcmVlYnNkLXBrZy8yMDI1LVNlcHRl bWJlci8wMDE1NTAuaHRtbD5dKGh0dHBzOi8vbGlzdHMuZnJlZWJzZC5vcmcvYXJjaGl2ZXMvZnJl ZWJzZC1wa2cvMjAyNS1TZXB0ZW1iZXIvMDAxNTUwLmh0bWwpLCBbPGh0dHBzOi8vbGlzdHMuZnJl ZWJzZC5vcmcvYXJjaGl2ZXMvZnJlZWJzZC1wa2cvMjAyNS1TZXB0ZW1iZXIvMDAxNTUzLmh0bWw+ XShodHRwczovL2xpc3RzLmZyZWVic2Qub3JnL2FyY2hpdmVzL2ZyZWVic2QtcGtnLzIwMjUtU2Vw dGVtYmVyLzAwMTU1My5odG1sKQo+Cj4+IFVuZGVyc3RhbmRpbmcgdml0YWwgd2l0aCB2ZXJzaW9u IDIuMi4yIG9mIHBrZyBpbiBGcmVlQlNEIDE2LjAtQ1VSUkVOVCAoMTYwMDAwMCkKPgo+IHBvbHlk dWVrZXMsIEkgc2hvdWxkIHJlY29tbWVuZCBhZGRpbmcgdGhlIGlzc3VlIHRvIEdpdEh1YiwgaWYg aXQncyBub3QgYWxyZWFkeSB0aGVyZSAoSSBkb24ndCBzZWUgaXQpLgo+Cj4gWzxodHRwczovL2dp dGh1Yi5jb20vZnJlZWJzZC9wa2cvaXNzdWVzP3E9aXM6aXNzdWUlMjBpczpvcGVuJTIwc29ydDp1 cGRhdGVkLWRlc2M+XShodHRwczovL2dpdGh1Yi5jb20vZnJlZWJzZC9wa2cvaXNzdWVzP3E9aXMl M0Fpc3N1ZStpcyUzQW9wZW4rc29ydCUzQXVwZGF0ZWQtZGVzYyk=

    --b1=_HpWCAuFtH7xV16aRW1lio0mQsdtTromdHLltjOmkmw
    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: base64

    PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5Pmkgd291bGQgbGlrZSB0byByZXBvcnQgaXQgYnV0IEkg d2FudGVkIHRvIGdhdGhlciBvcGluaW9ucyBvbiB0aGUgbWF0dGVyIG9mIEZyZWVCU0Qtc2V0LXNy YyBiZWluZyBtYXJrZWQgYXMgdml0YWwgZmlyc3Q8ZGl2IGNsYXNzPSJwcm90b25tYWlsX3F1b3Rl Ij4tLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPk9uIEZyaWRheSwgMTAvMTcv MjUgYXQgMDY6NDAgR3JhaGFtIFBlcnJpbiAmbHQ7Z3JhaGFtcGVycmluQGdtYWlsLmNvbSZndDsg d3JvdGU6PGJyPjxibG9ja3F1b3RlIGNsYXNzPSJwcm90b25tYWlsX3F1b3RlIj4NCiAgICA8ZGl2 IGNsYXNzPSJtb3otY2l0ZS1wcmVmaXgiPihSZWR1Y2VkIHRvIHRoZSBtYXhpbXVtIG9mIHR3byBs aXN0cyk8L2Rpdj4NCiAgICA8ZGl2IGNsYXNzPSJtb3otY2l0ZS1wcmVmaXgiPjxicj4NCiAgICA8 L2Rpdj4NCiAgICA8ZGl2IGNsYXNzPSJtb3otY2l0ZS1wcmVmaXgiPk9uIDE2LzEwLzIwMjUgMTk6 MjAsDQogICAgICA8YSBjbGFzcz0ibW96LXR4dC1saW5rLWFiYnJldmlhdGVkIiBocmVmPSJtYWls dG86cG9seWR1ZWtlc0Bwcm90b24ubWUiIHJlbD0ibm9yZWZlcnJlciI+cG9seWR1ZWtlc0Bwcm90 b24ubWU8L2E+IHdyb3RlOjxicj4NCiAgICA8L2Rpdj4NCiAgICA8YmxvY2txdW90ZSB0eXBlPSJj aXRlIj4NCiAgICAgIDxwcmUgd3JhcD0iIiBjbGFzcz0ibW96LXF1b3RlLXByZSI+4oCmIHRoZSAi MSBtaXNzaW5nIiByZWFsbHkgY29uZnVzZWQgbWUsIGlmIGl0IHdhc24ndCBmb3IgYSBoZWxwZnVs IGd1eSBmcm9tIHRoZSBjb21tdW5pdHkgaSB3b3VsZG4ndCBoYXZlIGZpZ3VyZWQgb3V0IHRoYXQg dGhlIGlzc3VlIHdhcyB0aGF0ICJGcmVlQlNELXNldC1zcmMiIGlzIG1hcmtlZCBhcyB2aXRhbCwg c28gaSB0aGluayBpdCB3b3VsZCByZWFsbHkgaGVscGZ1bCBpZiBpdCBpcyBwb3NzaWJsZSB0aGF0 IHBrZyBjYW4gdGVsbCB0aGF0IGluc3RlYWQgb2Ygc2F5aW5nICIxIG1pc3NpbmciPC9wcmU+DQog ICAgPC9ibG9ja3F1b3RlPg0KICAgIDxwPjxicj4NCiAgICA8L3A+DQogICAgPHA+KzE8L3A+DQog ICAgPHA+PGEgY2xhc3M9Im1vei10eHQtbGluay1yZmMyMzk2RSIgaHJlZj0iaHR0cHM6Ly9saXN0 cy5mcmVlYnNkLm9yZy9hcmNoaXZlcy9mcmVlYnNkLXBrZy8yMDI1LVNlcHRlbWJlci8wMDE1NTAu aHRtbCIgcmVsPSJub3JlZmVycmVyIj4mbHQ7aHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9hcmNo aXZlcy9mcmVlYnNkLXBrZy8yMDI1LVNlcHRlbWJlci8wMDE1NTAuaHRtbCZndDs8L2E+LA0KPGEg Y2xhc3M9Im1vei10eHQtbGluay1yZmMyMzk2RSIgaHJlZj0iaHR0cHM6Ly9saXN0cy5mcmVlYnNk Lm9yZy9hcmNoaXZlcy9mcmVlYnNkLXBrZy8yMDI1LVNlcHRlbWJlci8wMDE1NTMuaHRtbCIgcmVs PSJub3JlZmVycmVyIj4mbHQ7aHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9hcmNoaXZlcy9mcmVl YnNkLXBrZy8yMDI1LVNlcHRlbWJlci8wMDE1NTMuaHRtbCZndDs8L2E+PC9wPg0KICAgIDxwPg0K ICAgICAgPC9wPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPlVuZGVyc3RhbmRpbmcgdml0YWwgd2l0 aCB2ZXJzaW9uIDIuMi4yIG9mDQogICAgICAgIHBrZyBpbiBGcmVlQlNEIDE2LjAtQ1VSUkVOVCAo MTYwMDAwMCk8L2Jsb2NrcXVvdGU+DQogICAgPHA+PC9wPg0KICAgIDxwPjxicj4NCiAgICA8L3A+ DQogICAgPHA+cG9seWR1ZWtlcywgSSBzaG91bGQgcmVjb21tZW5kIGFkZGluZyB0aGUgaXNzdWUg dG8gR2l0SHViLCBpZg0KICAgICAgaXQncyBub3QgYWxyZWFkeSB0aGVyZSAoSSBkb24ndCBzZWUg aXQpLiZuYnNwOzwvcD4NCiAgICA8cD48YSBjbGFzcz0ibW96LXR4dC1saW5rLXJmYzIzOTZFIiBo cmVmPSJodHRwczovL2dpdGh1Yi5jb20vZnJlZWJzZC9wa2cvaXNzdWVzP3E9aXMlM0Fpc3N1ZStp cyUzQW9wZW4rc29ydCUzQXVwZGF0ZWQtZGVzYyIgcmVsPSJub3JlZmVycmVyIj4mbHQ7aHR0cHM6 Ly9naXRodWIuY29tL2ZyZWVic2QvcGtnL2lzc3Vlcz9xPWlzOmlzc3VlJTIwaXM6b3BlbiUyMHNv cnQ6dXBkYXRlZC1kZXNjJmd0OzwvYT48L3A+DQoNCg0KDQo8L2Jsb2NrcXVvdGU+PC9kaXY+DQog ICAgICAgICAgICAgICAgICAgIDwvYm9keT48L2h0bWw+


    --b1=_HpWCAuFtH7xV16aRW1lio0mQsdtTromdHLltjOmkmw--



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Lexi Winter@ivy@freebsd.org to muc.lists.freebsd.stable on Fri Oct 17 07:18:24 2025
    From Newsgroup: muc.lists.freebsd.stable


    --fg+ghEAvchr0YITA
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline

    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.

    --fg+ghEAvchr0YITA
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaPHfrAAKCRD1nT63mIK/ YPxyAQCXNl8RK88I/BK90FGQnoerz1k1j7iWVPi6gFeG0W+QiAD+LHApfR+/95GO 3A8BGyTGmOwmD+om0BIbc6uE3xIHFgI=
    =0RgK
    -----END PGP SIGNATURE-----

    --fg+ghEAvchr0YITA--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polyduekes@polyduekes@proton.me to muc.lists.freebsd.stable on Fri Oct 17 06:41:02 2025
    From Newsgroup: muc.lists.freebsd.stable

    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.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Lexi Winter@ivy@freebsd.org to muc.lists.freebsd.stable on Fri Oct 17 08:22:19 2025
    From Newsgroup: muc.lists.freebsd.stable


    --w3GQNYUyd3e2bp7H
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline

    polyduekes@proton.me wrote in <eReF1RJQrzi3aUqlXyr4rF3hFr32l2FlccEUOMfp9_Adpl7eQSPpfqTSUzdxzMGSs793h4IYqBSk5LdqVlr6t3_GNiBYlWZMwsmd-oTMD0Q=@proton.me>:
    pkg would autoremove the FreeBSD-set-src package or it's dependencies
    if it isn't marked as vital?

    the issue is that if you remove "src", intending to keep "src-sys", pkg
    will also remove "set-src", then since src-sys was autoinstalled as a dependency of set-src, a later "pkg autoremove" will remove src-sys,
    something the user probably didn't expect.

    the vital flag is intended as a safeguard to make people aware they
    might not want to do this.

    (i am not entirely convinced this actually fixes the problem, but the
    consensus was fairly strongly in favour of this.)

    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

    this is a reason to remove the src packages, not a reason to stop
    marking them as vital.

    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

    no, they won't: vital doesn't cause it to be automatically installed.
    if you have it installed, it's because you (or some tool, perhaps)
    opted to install it.

    --w3GQNYUyd3e2bp7H
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaPHuqwAKCRD1nT63mIK/ YCAFAQCix1X+Ge8Fqtfq99REMVv2lAM1M0K5opOHm9dgL0ZJ7AD9GiUc/ZK6Gdeg b49ICRixUX+idXpc4gPiMrR2o4bduQY=
    =5I0W
    -----END PGP SIGNATURE-----

    --w3GQNYUyd3e2bp7H--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polyduekes@polyduekes@proton.me to muc.lists.freebsd.stable on Fri Oct 17 10:44:28 2025
    From Newsgroup: muc.lists.freebsd.stable

    On Friday, October 17th, 2025 at 12:52 PM, Lexi Winter ivy@freebsd.org wrote:
    polyduekes@proton.me wrote in eReF1RJQrzi3aUqlXyr4rF3hFr32l2FlccEUOMfp9_Adpl7eQSPpfqTSUzdxzMGSs793h4IYqBSk5LdqVlr6t3_GNiBYlWZMwsmd-oTMD0Q=@proton.me:

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

    the issue is that if you remove "src", intending to keep "src-sys", pkg
    will also remove "set-src", then since src-sys was autoinstalled as a dependency of set-src, a later "pkg autoremove" will remove src-sys, something the user probably didn't expect.
    if a user wants to keep just the src-sys package they can simply remove the set and just pkg install the src-sys package, i am aware this isn't applicable to other sets but it quite fits for the src set

    the vital flag is intended as a safeguard to make people aware they
    might not want to do this.

    (i am not entirely convinced this actually fixes the problem, but the consensus was fairly strongly in favour of this.)

    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

    this is a reason to remove the src packages, not a reason to stop
    marking them as vital.
    the src package seems to be a nice addition for an user that installs freebsd with pkgbase and chooses to install the src tree as well, so it would be nice if it is possible to keep it only when the user chooses to :)

    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

    no, they won't: vital doesn't cause it to be automatically installed.
    if you have it installed, it's because you (or some tool, perhaps)
    opted to install it.
    you are right, sorry for the false assumption, guess the two issues i mentioned are on me then
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Lexi Winter@ivy@freebsd.org to muc.lists.freebsd.stable on Fri Oct 17 11:47:38 2025
    From Newsgroup: muc.lists.freebsd.stable


    --Ozx/riint+0EIu5Q
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    polyduekes@proton.me wrote in <cFqshZqdn372Bs2hGoWll9uJQq2SJ_a4Lkxo24L90lpL= asbUPVdK2QoIqNxfm1m9M6uFQo-udJpatkshM1gO9BsSnf88trbgn29FrPry_Vw=3D@proton.m= e>:
    On Friday, October 17th, 2025 at 12:52 PM, Lexi Winter ivy@freebsd.org wr=
    ote:
    the issue is that if you remove "src", intending to keep "src-sys", pkg will also remove "set-src", then since src-sys was autoinstalled as a dependency of set-src, a later "pkg autoremove" will remove src-sys, something the user probably didn't expect.
    =20
    if a user wants to keep just the src-sys package they can simply
    remove the set and just pkg install the src-sys package, i am aware
    this isn't applicable to other sets but it quite fits for the src set

    yes, this is the correct way to approach this for any set.

    although instead of using pkg install, you can just use pkg set -A0 to
    mark the package as not autoinstalled.

    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

    this is a reason to remove the src packages, not a reason to stop
    marking them as vital.
    =20
    the src package seems to be a nice addition for an user that installs
    freebsd with pkgbase and chooses to install the src tree as well, so
    it would be nice if it is possible to keep it only when the user
    chooses to :)

    i don't follow what you mean here. you just described the steps to
    remove FreeBSD-set-src earlier in your email. what else is needed
    here?

    --Ozx/riint+0EIu5Q
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaPIexwAKCRD1nT63mIK/ YKM+AP4ke9LZcjrIK9kvbMeDSyaQQZf18/aEwbMq0rTB6EOT8QD+Pe+5RqK8wmqU vLnlpZWxFptSATpZev6M71Ys/VR5/AQ=
    =MNUr
    -----END PGP SIGNATURE-----

    --Ozx/riint+0EIu5Q--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polyduekes@polyduekes@proton.me to muc.lists.freebsd.stable on Fri Oct 17 10:55:00 2025
    From Newsgroup: muc.lists.freebsd.stable


    Sent with Proton Mail secure email.
    On Friday, October 17th, 2025 at 4:17 PM, Lexi Winter <ivy@freebsd.org> wrote:
    polyduekes@proton.me wrote in cFqshZqdn372Bs2hGoWll9uJQq2SJ_a4Lkxo24L90lpLasbUPVdK2QoIqNxfm1m9M6uFQo-udJpatkshM1gO9BsSnf88trbgn29FrPry_Vw=@proton.me:

    On Friday, October 17th, 2025 at 12:52 PM, Lexi Winter ivy@freebsd.org wrote:

    the issue is that if you remove "src", intending to keep "src-sys", pkg will also remove "set-src", then since src-sys was autoinstalled as a dependency of set-src, a later "pkg autoremove" will remove src-sys, something the user probably didn't expect.

    if a user wants to keep just the src-sys package they can simply
    remove the set and just pkg install the src-sys package, i am aware
    this isn't applicable to other sets but it quite fits for the src set


    yes, this is the correct way to approach this for any set.

    although instead of using pkg install, you can just use pkg set -A0 to
    mark the package as not autoinstalled.

    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

    this is a reason to remove the src packages, not a reason to stop
    marking them as vital.

    the src package seems to be a nice addition for an user that installs freebsd with pkgbase and chooses to install the src tree as well, so
    it would be nice if it is possible to keep it only when the user
    chooses to :)


    i don't follow what you mean here. you just described the steps to
    remove FreeBSD-set-src earlier in your email. what else is needed
    here?
    sorry, i misunderstood "this is a reason to remove the src packages" statement, when i saw that i thought that you meant that reason deems to remove the src packages from the freebsd-base repo instead of removal from the user's system since at the time i wrote that i was considering that the src packages are autoinstalled
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2