56
submitted 10 months ago by cyberwolfie@lemmy.ml to c/linux@lemmy.ml

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?

all 28 comments
sorted by: hot top controversial new old
[-] premavansmuuf@lemmy.world 47 points 10 months ago

alias inkscape="flatpak run org.inkscape.Inkscape" into your .bashrc.

[-] cyberwolfie@lemmy.ml 10 points 10 months ago

Yeah, I tried this, and it works from my session, but I still got the same error from trying to run the program. I figured it was because it is called outside the bash session so the run commands have not been run, but is that perhaps not true?

[-] ForynGilnith@lemmy.world 40 points 10 months ago* (last edited 10 months ago)

If that's the case, it's a bit of an ugly hack but you could make a wrapper script placed in /usr/local/bin/inkscape like this:

#!/bin/bash

flatpack run org.inkscape.Inkscape ${*}

(the ${*} will pass along all the arguments that the wrapper script was called with)

[-] cyberwolfie@lemmy.ml 13 points 10 months ago

Thanks! I was trying to implement this, and was trying to figure out how to pass all the arguments! This worked for me! I got some other errors, but they don't seem related to this, so now to find out what they are all about 😅

[-] cybersandwich@lemmy.world 1 points 10 months ago

This is a great little hack.

[-] jsh@sh.itjust.works 1 points 10 months ago

Saving this for later, that's genius.

[-] ace@lemmy.ananace.dev 36 points 10 months ago* (last edited 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.pub 16 points 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.

[-] ace@lemmy.ananace.dev 1 points 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.

[-] OmnipotentEntity@beehaw.org 16 points 10 months ago* (last edited 10 months ago)

Put a shell script in your PATH named inkscape with the following content:

#!/bin/sh

flatpak run org.inkscape.Inkscape

Note that you can use a local folder in your home directory to house small executables and scripts like this, so you don't have to touch your system config. I generally recommend using something like ~/.local/bin and add it to your PATH via your Shell's RC file.

[-] cyberwolfie@lemmy.ml 4 points 10 months ago

How does this deal with any flags passed?

[-] OmnipotentEntity@beehaw.org 12 points 10 months ago* (last edited 10 months ago)

If you need to pass flags you can use

flatpak run org.inkscape.Inkscape "$@"

To forward all of the arguments to the script. Note that this might be a bashism, so you might need to change your hash bang to /bin/bash as well. Double check though.

(An easy way to check if something is working as you assume is just prepend the line with echo.)

[-] gnuhaut@lemmy.ml 4 points 10 months ago

This is not a bashism. It'll work fine with any sh.

[-] OmnipotentEntity@beehaw.org 1 points 10 months ago

Thanks, I wasn't sure it worked in sh. I've been surprised a lot before by seemingly simple stuff like this.

[-] SSUPII@sopuli.xyz 0 points 10 months ago

Or instead just make it an alias in your .bashrc

[-] smileyhead@discuss.tchncs.de 6 points 10 months ago

You can do an alias for the shell you use or make a symlink to /usr/local/bin/ for the entire system.

There are importany reasons why this is not the default, but you can do it as long as you are away you have done it. Like when programs installed via package manager and flatpak starts conflicting, you'll know why.

[-] Tzeentch@lemmy.blahaj.zone 6 points 10 months ago

Two utilities that may be handy for you here:

Pakrat: Automates and simplifies the process of creating alliases for flatpaks, good if you just need to make a few programs be simplified

Fuzzpak: Lets you do fuzzy searches for flatpaks(as in you just write fuzzpak inkscape and it auto looks for something with inkscape in the flatpak folder and launches it), good for when you want to simplify launching flatpaks in general without doing the process of configuring stuff manually

[-] Galli@hexbear.net 5 points 10 months ago
[-] hellvolution@lemmygrad.ml 4 points 10 months ago

You can use symbolic links, alias...

[-] GentooIsBased@lemmy.ml 2 points 10 months ago

I actually didn't know about the symbolic link meathod. Thanks!

[-] ad_on_is@lemmy.world 4 points 10 months ago

Why don't you check for both and use the one that's available, otherwise print an error. Additionally you could read an env INKSCAPE_BIN and also include that in your checks.

So one could for example do INKSCAPE_BIN='distrobox enter arch -- inkscape' python main.py

[-] cyberwolfie@lemmy.ml 2 points 10 months ago

It is not my package, but I could of course go ahead and change the source code directly to handle this. But I'd prefer a solution that would persist through updates.

[-] juli@programming.dev 1 points 10 months ago
this post was submitted on 31 Dec 2023
56 points (91.2% liked)

Linux

48335 readers
895 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS