Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Soren Stoutner Newsgroups: linux.debian.maint.python Subject: Re: python-pyinstaller: package naming questions Date: Thu, 31 Oct 2024 22:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Oct 31 21:27:06 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-114.93 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.421, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no Organization: Debian MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart432606945.ZL440uy7bS"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Debian-User: soren X-Mailing-List: archive/latest/22502 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/27471270.ZFbi4UoJAX@soren-desktop Approved: robomod@news.nic.it Lines: 80 Sender: robomod@news.nic.it X-Original-Date: Thu, 31 Oct 2024 14:26:40 -0700 X-Original-Message-ID: <27471270.ZFbi4UoJAX@soren-desktop> X-Original-References: <1974535.2LLsDtfzef@soren-desktop> Xref: csiph.com linux.debian.maint.python:16432 --nextPart432606945.ZL440uy7bS Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8"; protected-headers="v1" From: Soren Stoutner To: Debian Python Subject: Re: python-pyinstaller: package naming questions Date: Thu, 31 Oct 2024 14:26:40 -0700 Message-ID: <27471270.ZFbi4UoJAX@soren-desktop> Organization: Debian In-Reply-To: <1974535.2LLsDtfzef@soren-desktop> References: <1974535.2LLsDtfzef@soren-desktop> MIME-Version: 1.0 I didn=E2=80=99t receive any responses to the below email, so I decided to = go with=20 pyinstaller as the source package name, but to still use two binary package= s: =20 pyinstaller and python3-pyinstaller. On Friday, October 25, 2024 1:07:53 PM MST Soren Stoutner wrote: > I am in the process of packaging python-pyinstaller. >=20 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D1084906 >=20 > Currently my source package is named python-pyinstaller. It produces two > binary packages: >=20 > pyinstaller - installs executables to /usr/bin > python3-pyinstaller - installs Python modules to > /usr/lib/python3/dist-packages >=20 > I have been following the discussion about package names and have started= to > wonder if pyinstaller wouldn=E2=80=99t be a better source package name. = That is=20 what > it is called upstream, and the =E2=80=9Cpy=E2=80=9D prefix already indica= tes it is related to > Python. >=20 > Beyond that, I was wondering if it wouldn=E2=80=99t be better to only pro= vide one > binary file. I don=E2=80=99t know if there is any value to the Python mo= dules > without the executables in /usr/bin. Is there any policy or best practice > that says this should be split into two binary packages? >=20 > Soren >=20 > P.S. I figured I would ask now as it is easy to make changes before the = first > upload. =2D-=20 Soren Stoutner soren@debian.org --nextPart432606945.ZL440uy7bS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmcj9hAACgkQwufLJ66w tgPycRAAoWCZPLl2mfgdg19UI4AzCru6NklAX/lfuZ0CtdCPHe4BvAqnhaD98IrC UlYgMVQENHJ0JZ6IzyDV3aD+6mnW4cqF+ebY0ObuAQYyoICACc9F50KO/mO+ab6w TYy6pDcD1b5dqRr3U5PX8qqT/8jUyns5GkrmyYEBGM9xgiP925RUndvPxfQ0dEog /pj/e159oQDyAkfe6kUk4U2nOMD0YUkMX4a+8Z6ocfZ74NmXYaJuJ1zYoJ7qolUs eNeisFcQ1O05jVoom+rHkaIYYUQKNcAbBIPWfUVN/mdLUNNLHKAInLYYTTqesEdz mOjX5nZek1scjIlE5TS3heK9LvbTLPfg32a4lVfu+wtunubr5WkIrqEvD2Z6yIig WdLdCx6zIrm4pKpx2RAvM8C5vZ3uLzKlD6UmPcPtyHRVql/Qvmvc2cCjdfWeLaW6 qDjF1Lc0ZzkzXZSJHDNJCQpPvIf4+ACQ0F08N+cPL84vD5utsS/rsjWAhQiKFDOg fz6M5HVWJPr91Lj9MWlI4V9JQVQ+uaTuS05WWuxSVPG3e9KCN3ZulPAl/QamiOt+ SbicwCQSAqNIcvxFtkcB4Cy6IH1Q4B+z4vEBunWwnqkJTbZzQ9CDvQcDAwaRFZ3Z fOYv5WN72GDPfhNDuS28LSoOo93Dmu4CKuz5aulFzdnMMC17GxM= =SYN/ -----END PGP SIGNATURE----- --nextPart432606945.ZL440uy7bS--