Default configuration file override at run time about pitrery HOT 4 CLOSED

Hello,

If you are going to put CONFIG="x" on the same command line all the time, you can already do pitrery -f x check to get the same result.

With -f (or -c) x make pitrery search for /etc/pitrery/x.conf. If you put a path to a file, -f will use the file without search /etc/pitrery. You can change the directory by setting SYSCONFDIR in config.mk and have the rpm specfile apply a patch for this when building the rpm.

Regards,

from pitrery.

@orgrim, that's an example among others of how that could be used.

I know about the SYSCONFDIR, I'm using it already, like I said I'm modifying the config directory already when building the rpm file we are distributing, but I'd also like to be able to override the configuration file name.

from pitrery.

I guess I lack some context, but personnally, I feel safer with the command line switch than the environment. At least, it would be better to choose a name that is less prone to collisions than CONFIG.

from pitrery.

Sure @orgrim CONFIG was just an example, it would have to be more specific to Pitrery.

from pitrery.