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

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

Python/LibraryStyleGuide: Executables and library packages dokonana przez BarryWarsaw

Show key headers only | View raw

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

[Debian Wiki, 2015-10-07]
> https://wiki.debian.org/Python/LibraryStyleGuide?action=diff&rev1=64&rev2=65
> 
>   
>   == Gotchas ==
>   
> + === Executables and library packages ===
> + 
> + Let's say you have a Python package which results in Python 2 and 3 libraries, and a Python 3 executable.  What is the best practices for naming and organizing your binary packages?
> + 
> + Clearly you want to have:
> + 
> +  * python-foo -- the Python 2 library
> +  * python3-foo -- the Python 3 library

     * foo -- for the executable (and possible additional dependencies that library doesn't need)

maybe extent it to:

     * python-foo -- the Python 2 library (and Python 2.X scripts if they're Python 2.X specific)
     * python3-foo -- the Python 3 library (and Python 3.X scripts if they're Python 3.X specific)

> + 
> + but where should the `/usr/bin/foo` script go?  You could put it in `python3-foo` but you '''CANNOT''' put it in `python-foo` or for that matter any binary package that starts with the `python-` prefix.  `dh_python3` refuses to rewrite shebang lines for any executable in a binary package that starts with "python-" or "pypy-".  This means that something like `python-foo-cli` or `python-foo-bin` is unacceptable.

I'd remove this part - it's not dh_python3 specific (dh_python2 and
dh_pypy does similar things) and I don't think such corner case should
be in style guide

> + 
> + Here are some recommendations.  We do not have a standard (though maybe we should):
> + 
> +  * `foo` - this is nice if it parallels the /usr/bin/foo name but it might collide with existing packages, and some people don't like to make such a claim on an unadorned top level package
> +  * `python3-foo-cli` or `python3-foo-bin` - not as nicely discoverable, but `command-not-found` can help, and dh_python3 will work

if someone creates python3-foo-cli binary just to ship /usr/bin/foo it
might as well be foo (if there are no /usr/bin/foo name collisions,
binary package name should be safe as well) so I'd remove it
-- 
Piotr Ożarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar

Thread

Python/LibraryStyleGuide: Executables and library packages dokonana  przez BarryWarsaw Piotr Ożarowski <piotr@debian.org> - 2015-10-07 23:40 +0200
  Re: Python/LibraryStyleGuide: Executables and library packages  dokonana przez BarryWarsaw Barry Warsaw <barry@debian.org> - 2015-10-08 00:10 +0200

csiph-web