Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README notes - problem with Inkscape from Snap package. #6

Open
MarcinOrlowski opened this issue Jan 31, 2023 · 3 comments
Open

README notes - problem with Inkscape from Snap package. #6

MarcinOrlowski opened this issue Jan 31, 2023 · 3 comments

Comments

@MarcinOrlowski
Copy link

MarcinOrlowski commented Jan 31, 2023

Not really an issue but you might want to update the README with the notes that using Inkscape installed as Snap package is currently not supported by this script. It looks like that particular type of packaging affects applications' working directory, because in my case Inkscape was looking for the svg/templates.svg relative to my home directory (~) and not my actual working directory. Probably using absolute paths all over the code would solve the problem, but I reinstalled Inkscape from "native" package and that worked for me.

Also a note that xcursorgen on Debian/Ubuntu etc is part of x11-tools package could probably be useful.

@MarcinOrlowski MarcinOrlowski changed the title README notes README notes - problem with Inkscape from Snap package. Feb 2, 2023
@charakterziffer
Copy link
Owner

Thank you, Marcin, for being that attentive and for filing this report!

Could you give me some more information, please? Is this seen as a bug of the snap package to be resolved? Is there an official bug report to estimate how long this problem will persist?

Working with absolute paths would limit the flexibility for all users because then they always have to place the folder in a certain location (and e.g. not on ~/Desktop). But maybe a hint in my README could say that users of the snap package must place the contents directly into the home directory until this issue is solved. Or is there another possibility, e.g. predefine the path of the working directory for snap users?

If added the info about the x11-tools package, good idea, thank you!

@MarcinOrlowski
Copy link
Author

Is this seen as a bug of the snap package to be resolved?

I tried it with recent version so I do not think anything changed. I am not sure it's a bug technically or maybe limitation (feature?) of snap (i.e. IIRC snaps cannot reach /tmp as these have own, isolated folder etc). So maybe it works as expected for some reasons yet I spent a while figuring that out, hence my comment.

Working with absolute paths would limit the flexibility for all users because then they always

I wasn't precise enough perhaps. I am not saying you should require user to pass absolute path. Instead I suggested that all paths are absolute internally (so you resolve CWD and append to the path etc). That should work around the snap issue. But still, I'd probably just edit the README and forget :)

@charakterziffer
Copy link
Owner

Ah, now I hopefully get to understanding: Users of the snap installed Inkscape are not able to use the commands as I list them in the README, but they have to change the paths to absolute ones. So instead of ./render-pngs.py svgs/template.svg they should type ./render-pngs.py /home/username/path-to-the/svgs/template.svg … Is that correct?

Or do all the paths (e.g. in the hotspot or render-pngs file) also be absolute and depending at the location of the folder on the users computer? What do you mean by absolute internally? Without knowing the folder’s location I can’t give absolute paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants