You are not logged in.

#1 2007-04-18 19:32:22

anakin
Member
From: Portugal
Registered: 2006-09-11
Posts: 85
Website

Hard coded "/etc/opt/pkgname/..."

I've been working on a PKGBUILD which now I'd like to submit to the AUR. It's a standalone package thus it perfectly fits under "/opt" which it actually uses as its file structure, except for one detail which I'll let you know below.

Having gone through the documentation and guidelines on the wiki I didn't find an obvious answer to what's the best practice towards software featuring a binary distribution (no sources available) which has a conf path like "/etc/opt/pkgname/..." hard coded into the binary instead of the standard "/opt/pkgname/etc".

Installing the conf files in the right place ("/opt/pkgname/etc") and making some symbolic link trickery under "/etc" seems more reasonable though it's still not standard.

What's the right way?


www.geekslot.com - a place where peculiar people fit

Offline

Board footer

Powered by FluxBB