[Slackbuilds-users] yt-dlp release

[Eugen Wissner]

Well python binaries have a suffix, /usr/bin/python3.12,
/usr/bin/python3.12-config. Then there are symlinks, /usr/bin/python3
and /usr/bin/python, that point to the default python version
(/usr/bin/python3.9 in the case of Slackware stable). So different
python versions shouldn't conflict and the software would still use 3.9
by default.

A lot of people seem to disagree but I prefer to install software in
default /usr locations if possible. Python supports suffixes, so why use
/opt. But I'm not a Python programmer, maybe I'm missing something. But
my script from the previous email installs python into /usr/ but doesn't
override standard python.

On Fri Oct 24, 2025 at 12:16 AM CEST, Antonio Leal via SlackBuilds-users wrote:
> Having the latest python is tempting... totally agree.
>
> But who ensures its does not break stock slackware programs that depend 
> on 3.9?
>
> If the issue is just one app wouldn't a python venv be enough?
>
>
> On 10/23/25 10:08 PM, B. Watson wrote:
>>
>>
>> On Thu, 23 Oct 2025, fourtysixandtwo wrote:
>>
>>> I've been thinking about this off and on for a while and have a few
>>> ideas about it.
>>>
>>> -If we do this 3.12 should be the target (like current)
>>> -It doesn't have to live in /opt necessarily
>>> -we could have the existing slackbuilds also build for 3.12 if it's
>>> installed (or as necessary) which would allow just rebuilding existing
>>> slackbuilds without duplicating every python slackbuild.  (other than
>>> the stock slackware python builds we don't have "-opt" versions for)
>>>  -this option would have other concerns so I'm not sure it's viable,
>>> (Eugene: like affecting my recent sbotools suggestion)
>>>  -would be a bit messier like the pre python2/3 split slackbuilds
>>>  -it would however be easier to manage I think (less duplication of
>>> work required)
>>
>> All this makes sense.
>>
>> It can be viable.
>>
>> I was thinking /opt because there might be some random piece of
>> software that would see /usr/bin/python3.12 and decide to build itself
>> against that instead of respecting the /usr/bin/python3 symlink.
>> Using /opt would keep it out of the way, so installing the new python
>> wouldn't affect anything else.
>>
>>> Of course if we knew if the next release of Slackware was imminent
>>> this wouldn't be a concern.  I would hate to do the work on this then
>>> have that drop shortly after.
>>
>> Yeah.
>>
>> Going by how long the last Slackware release took, we probably have
>> at least a couple more years before the next one.
>>
>> It's almost 100% certain that PV won't do a release until he has
>> KDE/Plasma 6, and the KDE in -current is still 5. So I'm going with
>> "it'll be a while yet". I'd love to be proven wrong though.
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/