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

using proper paths for ressources #22

Open
umlaeute opened this issue May 18, 2017 · 7 comments
Open

using proper paths for ressources #22

umlaeute opened this issue May 18, 2017 · 7 comments

Comments

@umlaeute
Copy link
Contributor

IanniX tries to locate it's ressources (e.g. the Museo.ttf font, but also others) in a path relative to the iannix binary.
Unfortunately it uses a subdirectory of the iannix path.

after doing a make install, this means that a path like /usr/local/bin/Tools/Museo.ttf is searched.
this is in violation of the FHS: ressources should be located in /usr/local/lib/iannix/ (and /usr/local/share/iannix/ for non-binaries).
They should definitely not be in a subdirectory of bin/!

@umlaeute
Copy link
Contributor Author

Actually, the search-path is constructed via Application::pathApplication.absoluteFilePath() + "/Tools/", so it should be pretty easy to make the current behaviour overridable somewhere around iannixapp.cpp:100.

@domichel
Copy link

domichel commented Aug 1, 2017

I fully agree with umlaeute, As pointed out, it is some standards on GNU/linux. One of them is that /usr/bin should only contain executable files and no sub-directory at all. This help to insure the coherence of the system. That imply iannix should definitely look somewhere else for its resources.

BTW: Thanks for the good work!

@dvzrv
Copy link

dvzrv commented Mar 25, 2018

Any update on this? This pretty much makes it impossible to ship iannix as a package on Linux.

@umlaeute
Copy link
Contributor Author

@dvzrv well, iannix is already shipped as a Debian package, so it is obviously possible to ship it as a package "on Linux" (although the Debian package fixes the problem)

@dvzrv
Copy link

dvzrv commented Mar 25, 2018

@umlaeute I only have limited time on my hands and patching something, that should be fixed upstream is a little out of scope for me currently.
I'd gladly take a look at the package you provide for Debian though!

@umlaeute
Copy link
Contributor Author

sure. also i'm not saying that this shouldn't be fixed upstream.
(i was mainly commenting on the somewhat exclusive use of "Linux" to mean your favorite distro :-))

@dvzrv
Copy link

dvzrv commented Mar 25, 2018

(i was mainly commenting on the somewhat exclusive use of "Linux" to mean your favorite distro :-))

LOL. Glad we have that settled then.

Note: I was referring to the workload that is put on a package maintainer, because of issues, such as this. That has nothing to do with whatever distribution you're using, as the applying of x patches is always going to require time.
I'm sorry, if that was misread as a distribution flamewar attempt or something like that. I should have been more specific as in:

This pretty much makes it very painful to ship iannix as a package on Linux (unless you're really into patching ;-) ).

That being said, would it be possible for you to upstream some of the patches you apply for Debian?

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

3 participants