1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.PYTHON

  • can one change the path of generated entry point console_scripts

    From Philippe Cerfon@21:1/5 to All on Tue Feb 14 01:40:02 2023
    Hey.

    When I use dh-python to build a package that contains a pyproject.toml
    and uses python3-setuptools for building like e.g. described here https://setuptools.pypa.io/en/latest/userguide/entry_point.html

    and I use that entry point feature to have a script auto-generated
    that calls my main():[project.scripts]
    somescript = "package:main"

    is it possible to change the path were that script is finally put it
    the package (i.e. not ./usr/bin/)?

    I tried to look it up in other Debian source packages, but all that I
    checked and which contain Python scripts in non-/usr/bin locations
    simply put a real file there, and not such a auto-generated one.


    Thanks,
    Philippe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefano Rivera@21:1/5 to All on Wed Feb 15 17:40:02 2023
    Hi Philippe (2023.02.14_00:13:08_+0000)
    When I use dh-python to build a package that contains a pyproject.toml
    and uses python3-setuptools for building like e.g. described here https://setuptools.pypa.io/en/latest/userguide/entry_point.html

    and I use that entry point feature to have a script auto-generated
    that calls my main():[project.scripts]
    somescript = "package:main"

    is it possible to change the path were that script is finally put it
    the package (i.e. not ./usr/bin/)?

    Just move it somewhere else later in the build? e.g. after dh_install.

    /usr/bin is where user-executable scripts should go, unless they belong
    in /usr/sbin or /usr/games.

    Internal scripts (that will be executed by the full path name) can live
    in /usr/share/<packagename> or similar.

    SR

    --
    Stefano Rivera
    http://tumbleweed.org.za/
    +1 415 683 3272

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Philippe Cerfon@21:1/5 to stefanor@debian.org on Fri Feb 17 03:10:01 2023
    Hey Stefano

    On Wed, Feb 15, 2023 at 5:37 PM Stefano Rivera <stefanor@debian.org> wrote:
    Just move it somewhere else later in the build? e.g. after dh_install.

    I had tried that before, with a debian/mypackage.install file but got
    an error that it doesn't find the file.
    Then I realized that I cannot use e.g.:
    usr/bin/script usr/sbin/
    but have to use:
    debian/mypackage/usr/bin/script usr/sbin/
    in the .install file.

    Is that the right way? Or is there a more proper "way"?


    Thanks,
    Philippe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Philippe Cerfon on Fri Feb 17 10:00:02 2023
    On Fri, Feb 17, 2023 at 02:49:49AM +0100, Philippe Cerfon wrote:
    Hey Stefano

    On Wed, Feb 15, 2023 at 5:37 PM Stefano Rivera <stefanor@debian.org> wrote:
    Just move it somewhere else later in the build? e.g. after dh_install.

    I had tried that before, with a debian/mypackage.install file but got
    That's not what "move it [...] after dh_install" means, it usually means a manual mv call.

    an error that it doesn't find the file.
    Then I realized that I cannot use e.g.:
    usr/bin/script usr/sbin/
    Yes, .install is not for moving files between directories inside a
    package. Please check its two use cases in dh_install(1).

    but have to use:
    debian/mypackage/usr/bin/script usr/sbin/
    I don't think this is a good idea.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)