I have a Python-package that calls Inkscape as part of a conversion process. I have it installed, but through Flatpak. This means that calling inkscape does not work in the terminal, but rather flatpak run org.inkscape.Inkscape. I need the package to be able to call it as inkscape.

What is the best way to go about this?

  • Ananace@lemmy.ananace.dev
    372·
    10 months ago

    Flatpak already creates executable wrappers for all applications as part of regular installs, though they’re by default named as the full package name.

    For when inkscape has been installed into the system-wide Flatpak installation, you could simply symlink it like; ln -s /var/lib/flatpak/exports/bin/org.inkscape.Inkscape /usr/local/bin/inkscape

    For the user-local installation, the exported runnable is in ~/.local/share/flatpak/exports/bin instead.

    • rotopenguin@infosec.pubEnglish
      16·
      10 months ago

      I handle it more like ln -s /var/lib/flatpak/exports/bin/org.inkscape.Inkscape ~/.local/bin/inkscape

      .local/bin is a directory that you may have to make, but your shell’s startup scripts should automatically add it to the PATH after that.

      • Ananace@lemmy.ananace.dev
        1·
        10 months ago

        I personally use ~/.bin for my own symlinks, though I also use the user-specific installation instead of the system-wide one.
        I wouldn’t guarantee that any automation handles ~/.local/bin or ~/.bin either, that would depend entirely on the distribution. In my case I’ve added both to PATH manually.