Petter Reinholdtsen wrote:
> As we discussed on IRC, I'm not too happy about adding yet another
> extension to cdebconf, and thus making it divert even further away
> from debconf and the official debconf protocol.
I understand your concerns, certianly..
> What about creating a few new debconf templates which content point to
> another template? Something like debconf/bordertitle set to
> mypkg/bordertitle, which in turn contain the translated text. We
> could use this instead of the SETTITLE command (which I never was
> happy with because it created yet another command not listed in the
> protocol specification), and perhaps add a feature to show
> installation notes while the installer is busy doing package
> installation.
The only reason that SETTITLE is not documented in policy is because I
seem to be incapable of getting seconds to my policy proposals anymore,
don't see any real activity at all on policy, and so have given up on
getting any changes in. As far as I'm concerned it's part of the spec
now.
> cdebconf would then need to look up the template pointed to by its
> "internal" templates (like debconf/bordertitle) every time the
> translation language changes, and every time the value changes.
The problem with going this route is that debconf implementations have
to then have support for hooks to inform the frontend when a value in
the database is changed. Besides being rather clumsy to implement in
debconf (or at least, likely to take a lot of new code), I think it has
some real problems when deconf is using a remote database. Especially if
more than one debconf instance is talking to the same database.
I also think it's nice the way the spec currently imposes essentially no
policy on question namespace. This allows debconf users to be very
flexible in how they split up the namespace. The few values under
debconf/* that do have defined values in debconf have tended to create
lots of implementation special cases and problems[1], and so I am leery
of more of them.
--
see shy jo
[1] Most notably I've tried several times to clean up how debconf
handles temporary overrides to debconf/priority etc that need to
apply during a single run, so that if you dpkg-reconfigue -plow
or whatever, accesses to debconf/priority will show it has that
value instead of the permanent one in the db. My attempts have
failed.
Attachment:
signature.asc
Description: Digital signature