[Debconf-devel] Bug#511889: debconf: Allow different file and package name in frontend initialization

Davor Ocelic docelic at spinlocksolutions.com
Thu Jan 15 12:45:13 UTC 2009


Package: debconf
Version: 1.5.24
Severity: wishlist
Tags: patch


Hello,

In the current frontend selection mechanism, saying --frontend=gnome
unconditionally assumes the frontend should be loaded from
FrontEnd/Gnome.pm and have a package name Debconf::FrontEnd::Gnome.

However, it is handy to allow the file and package to have different
names (Set filename to your customized frontend, and package name to
existing frontend's name).

That way, you can override/extend parts of an existing frontend with
great ease, and use all other parts as-is.

The simple patch attached allows Debconf to use a different file and
package name when selecting and initializing the frontend.

The functionality is accessed by specifying '=' in the frontend name.

So, a setting of --frontend frontend2=gnome has the following effect:

  File to "use": FrontEnd/Frontend2.pm
  Package to call "->new" on: Debconf::FrontEnd::Gnome

Thanks,
Davor Ocelic
docelic at spinlocksolutions.com
http://www.spinlocksolutions.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debconf-1.5.24-frontend_name.patch
Type: text/x-patch
Size: 1195 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/debconf-devel/attachments/20090115/732ee726/attachment.bin 


More information about the Debconf-devel mailing list