You are not logged in.
Hi there
I made a PKGBUILD for sp-tk (speek toolkit).
It provides LOTS of binaries.
Of course the name of one of them is conflicting with a binary of another package (boost)
I thought of two options:
1. installing it in /opt instead of /usr (rather simple): but there may be conflicts with other packages (not that I am aware of)
2. putting the binaries in its own repository (e.g. /usr/share/sptk/bin or /opt/sptk/bin) and adding a profile.d/sptk.sh script to include the binary locations in the path.
What would be the best approach? (Any other good suggestion accepted)
Thanks,
Seb
Offline
/opt is best, and if you put everything under /opt/sp-tk there will be no conflict. I recall seeing when I first started packaging, though, that AUR packages should not put anything in /opt for FHS reasons (some of my own packages were threatened with deletion because of that).
Is this program open-source or binary-release?
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Thank you!
It is open source, under some BSD license.
So if I put everything under /opt/sp-tk it will create the corresponding bin,lib,include dirs.
I have now other questions
- It is not an every day software: those are speech processing tools, so I don't have to create a profile.d/sptk.sh to get access to the binaries, do I?
- Is the license still under /usr/share/licenses/sptk/ ?
Offline
You could also just rename the binary that conflict.
Offline
Well it is not convenient. These are tools, which are usually used by other software/scripts. So changing the name of the binary would impact all the scripts based on it
Offline
Well it is not convenient. These are tools, which are usually used by other software/scripts. So changing the name of the binary would impact all the scripts based on it
In that case, you'll need profile.d/sptk.sh to update the PATH variable otherwise the software/scripts won't find the sptk tools unless they specify the correct full path.
And the license still goes in /usr/share/licenses/sptk/ (assuming sptk is the pkgname)
Offline
Discussion following there:
https://bbs.archlinux.org/viewtopic.php?pid=1003397
Offline