Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #16401

python-pyinstaller: package naming questions

From Soren Stoutner <soren@debian.org>
Newsgroups linux.debian.maint.python
Subject python-pyinstaller: package naming questions
Date 2024-10-25 22:10 +0200
Message-ID <JByNb-4c5C-7@gated-at.bofh.it> (permalink)
Organization Debian

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

I am in the process of packaging python-pyinstaller.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084906

Currently my source package is named python-pyinstaller.  It produces two binary 
packages:

pyinstaller - installs executables to /usr/bin
python3-pyinstaller - installs Python modules to /usr/lib/python3/dist-packages

I have been following the discussion about package names and have started to wonder if 
pyinstaller wouldn’t be a better source package name.  That is what it is called upstream, 
and the “py” prefix already indicates it is related to Python.

Beyond that, I was wondering if it wouldn’t be better to only provide one binary file.  I don’t 
know if there is any value to the Python modules without the executables in /usr/bin.  Is 
there any policy or best practice that says this should be split into two binary packages?

Soren

P.S.  I figured I would ask now as it is easy to make changes before the first upload.

-- 
Soren Stoutner
soren@debian.org 

Back to linux.debian.maint.python | Previous | NextNext in thread | Find similar | Unroll thread


Thread

python-pyinstaller:  package naming questions Soren Stoutner <soren@debian.org> - 2024-10-25 22:10 +0200
  Re: python-pyinstaller:  package naming questions Soren Stoutner <soren@debian.org> - 2024-10-31 22:30 +0100

csiph-web