Paul D. Smith writes:
> pe> The last thing I want is each documentation format claiming its
> pe> own major directory in the file system.
>
> Um... why not?
Because the set of possible documentation formats is infinite for all
practical purposes. Perhaps not in the pedantic GNU system, but
[ On , August 24, 2000 at 23:33:32 (-0400), Paul D. Smith wrote: ]
> Subject: Re: HTML format documentation
>
> %% [EMAIL PROTECTED] (Greg A. Woods) writes:
>
> >> Moving man to .../share (${datadir}) on some systems was painful
> >> enough, and there was a very solid technical reason to do t
Whether to use /usr/share/doc instead of /usr/doc is a decision I will
have to think about. "Standards" written for the GNU system by people
who are not participating in the GNU Project, and who don't even
recognize that the system is GNU, have no authority here. Please do
not change this now.
What's the current "best practices" for handling RC and config files?
I gather the GNU coding standards say one should not hardcode paths into the
software, but I haven't seen anything written about good ways to handle
runtime configuration.
Has anybody written anything up on this stuff?
H
I'll be a little more specific.
I want to have different versions of a package installed. This package
needs an RC file, and verious programs in the package need to call each
other.
There are cron jobs that need to be run on behalf of the package, and it
runs network daemons that call programs.
