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
pagkages with additional symlinks #7
Comments
Hi @atticus-sullivan, sorry for the delayed response. Yes this is doable but its not generic... We can scan the I too am not sure what would be a good solution, I suspect the only option is add some internal configuration of |
Oh no worries, it's open source and we all want to have fun in our free time. So there is nothing in putting any stress to yourself. The advantage, fixed packages like Maybe we can develop various heuristics when to link scripts But maybe this thought is to optimistic as there are (and there will be more) packages like cluttex which provides no man-pages and I see no other detail which indicates this is a script which should be linked. So in the end I've got no real/working idea either how to do this without hard-coding what to link (though writing some sort of config with what to link, we might use the official arch packages as a starting point). Sadly, I have no clue about perl, so I'm afraid I can't really help you in implementing (at most discussing design decisions 🤷) |
I've used
tllocalmgr
to install theglossaries
tex package but I'm missing the symlink to some location in thePATH
formakeglossaries
some other packages (if installingglossaries
via e.gtexlive-latexextra
) contain. I can imagine there are some other tex packages which contain executables and/or scripts for which symlinks to some folder in thePATH
would be nice.To be honest I'm not sure how to implement this, this is just an obversation/whish.
Maybe we can search if the tex package adds files to
/usr/share/texmf-dist/scripts/
and symlink these (most probable to something like/usr/local/bin
), but I'm not sure if this will work (don't know the internals oftllocalmgr
).The text was updated successfully, but these errors were encountered: