Date: Fri, 30 Sep 2022 12:43:33 -0700 From: Dan Mahoney <freebsd@gushi.org> To: Stefan Esser <se@freebsd.org> Cc: ports@freebsd.org, Alexander Leidinger <Alexander@leidinger.net> Subject: Re: Python version dependencies in pkg Message-ID: <5CDB69DD-4DD9-4276-BF80-71DB63403458@gushi.org> In-Reply-To: <2c373ee2-785b-d31f-23d3-bc0856c7bf5e@FreeBSD.org> References: <8B490359-27A3-410C-AE98-C1362D4FA9F0@gushi.org> <CAN6yY1sGnDF-oReRMFeVz78oGoTfUvsvwUOQwoBZWN9ibjTw3A@mail.gmail.com> <B2A3A400-F21A-4E92-8116-41E7945E4E5C@gushi.org> <CAN6yY1ujCH9Xnv3QN-GF8hN75v%2BxGkOTHrsr25jzxGNGdYW2vQ@mail.gmail.com> <89D2B2D7-FA3D-46F5-A93B-4846950A157C@gushi.org> <65597c37-813b-d0ed-ea9f-8591b68cf097@gwdg.de> <20220929083939.Horde.Viq2uLBgUctcrsgmaJxN_1u@webmail.leidinger.net> <F4395689-FFD7-4591-BE5C-3F15983BF82D@gushi.org> <2c373ee2-785b-d31f-23d3-bc0856c7bf5e@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 29, 2022, at 14:21, Stefan Esser <se@freebsd.org> wrote: >=20 >=20 >> But trying to do a pkg delete python3.8 attempted to delete = bind-tools, and I was looking for the magic incantation that says = "without reinstalling bind-tools, how can I re-point it at the python39 = variants of that package". On a box without a ports tree. Only using = pkg. >=20 > As you say, bind-tools does no longer depend on Python and therefore = is > not a good example. You're correct, but it was the [most recent] one that sent us down this = rabbit hole, so I'm using it. > But you can use the above command to query the python dependency for = any > pre-built package. >=20 > And no, you cannot "re-point" a package. "Re-pointing" is done by = building > the package with different default versions, and you can do it = yourself, > if the official version do not match your requirements. That goes against the whole recommendation of "don't mix ports and = packages", which means I'd be building everything from gcc on up to = solve this. We have a large enough install base and we're familiar with = poudriere that yes, we could do these things if we have to, but it would = be a pain point. Ah well. At this point I can count three times in recent history (with = three different packages) where a changing default has burned us, and I = have some suggestions for improvement that I'm trying to organize, but = now that I understand how defaults are baked in to packages, I have a = greater understanding of the problem to be solved/worked around/just = accepted. Thanks to everyone who responded. Best, -Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5CDB69DD-4DD9-4276-BF80-71DB63403458>