[Slackbuilds-users] Merging python / python3 packages

David Demelier markand at malikania.fr
Thu Feb 21 10:20:04 UTC 2019

Le 21/02/2019 à 01:32, Daniel Prosser a écrit :
> I like the idea of having a single script for both Python 2 and Python 3 
> versions of each module (or as many as possible), but I don't think a 
> lot of work should be done to enforce uniformity for 14.2. When 
> Slackware 15 comes out, Python 3 will be included and the issue of 
> dependencies will be moot for most scripts. For now, I can deal with 
> maintainers taking different approaches.

Won't it require lot of a time to do the merge for 15.0? I mean, how 
long are freeze times before a new Slackware version?

That's why I thought the master git branch was used to track 
slackware-current. Now I feel like once we have a code freeze in 
Slackware, we need to do as quick as possible the modifications in 
master to match the new upcoming release.

Or perhaps I understood something wrong.


More information about the SlackBuilds-users mailing list