You are not logged in.
I'm trying to make a package for libbow.
The code is quite legacy. However I managed to make it compile.
Now the problem is that it's using some modified version of argp which is part of libc. So if I stick to the package etiquette, there would be conflicts with the system files.
So should I install the software in /usr/local now?
Actually I'm quite curious what is the motivation of this rule.
Thanks!
Offline
FHS, I believe. /usr/local is for the user of the system to install his own software. When you make a package, you're considered a packager/distributor and so what you distribute must not (potentially) conflict with the user's own software.
Probably possible to install to /opt?
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
FHS, I believe. /usr/local is for the user of the system to install his own software. When you make a package, you're considered a packager/distributor and so what you distribute must not (potentially) conflict with the user's own software.
Probably possible to install to /opt?
Thanks, I understand now. However /opt is usually for binary install, right?
But I guess it's the best solution now.
Offline
It's not necessarily for binary installs only. Basically anything that doesn't fit in the "normal" layout usually gets put there.
So all in all, your best/cleanest solution is probably to use /opt here indeed.
Burninate!
Offline