Linux

47341 readers

1332 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Make Inkscape installed through Flatpak callable in the terminal as 'inkscape'? (lemmy.ml)

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

24 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] ad_on_is@lemmy.world 4 points 8 months ago (1 children)

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 8 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.