Re: Announcing debconf, configuration management for debian
Joey Hess <joey@kitenet.net> writes:
> Steve Greenland wrote:
> > I've read (or at least skimmed) the tutorial you posted, and it
> > looks like the various configuration variables are associated with a
> > package via the template "foo/variable". What about variables that are
> > logically shared between packages, such as the default directory for
> > the webservers, or news server name, and such. Is it acceptable for the
> > group of affected maintainers to use the virtual package name as the
> > variable package name? Or would some other way be better?
>
> I think we'll eventually let the policy group deal with this. For now there
> really arn't any rules, just common sense. Yes, I think it's acceptable to
> use virtual package names.
>
> The two packages I have now that share a variable name and slrn and
> slrnpull, they use news/server, which isn't exactly mapped to a virtual
Presumably variable names can have more than one / in them ?
If so, it might be worth calling such variables something like:
shared/news/server
to avoid name space pollution, and to emphasise the fact that there is
not a package called ``news'' (virtual or otherwise).
Cheers, Phil.
Reply to: