"Corey Crawford" <[EMAIL PROTECTED]> writes:
[snip]
> However, if it's done right then packages can be moved to this system one at
> a time without requiring any kind of rewrite for the portage system. Just
> somewhere along the line when you did an 'emerge sync' the new ebuild file
> and configuration file would be included.
Okay.
> The .defaults file is designed to be overwritten each time an 'emerge sync'
> is done. Just like the ChangeLog file is overwritten when it's
> changed.
> However, the .custom configuration file could easily go into an /etc
> directory (with make.conf would make sense). If there is no .custom file for
> the package being built (which would be checked by the package's ebuild)
> then the .defaults file would provide all the configuration values the
> ebuild needs.
This seems reasonable.
> A default .custom file does not need to be provided. The user can create
> their own .custom file with the variables they want to change from the
> .defaults file.
> I could probably convert Apache2's ebuild file to use this system in less
> than an hour.
This system can actually, to some extent, be implemented under the
existing system in the following manner:
Rather than have a `defaults' file, the ebuild can contain the
defaults. They would be programmed in a manner like this:
[ -z "${THE_VARIABLE}" ] && THE_VARIABLE="THE DEFAULT"
In order to avoid name clashes, however, each package-specific variable
would need to be prefixed. For example,
APACHE2_DOCUMENT_ROOT="whatever"
Under the current system, this could be added by users to make.conf.
If package-specific configuration files were supported, the variable
could simply be named DOCUMENT_ROOT and could be specified in a
configuration file with package scope.
--
Jeremy Maitin-Shepard
--
[EMAIL PROTECTED] mailing list
