Bug#38703: debian-policy: [PROPOSAL] A better way to configure debian systems
Peter S Galbraith <GalbraithP@dfo-mpo.gc.ca> writes:
> > The configure script must be a bash script, but not everything allowed
> > in bash is allowed there.
>
> Excuse my ignorance... Is this for postinst scripts or
Thats for the configure scripts in the controll.tar.gz. The postinst
scripts must not change the configuration of a package.
> /usr/sbin/*config scripts or both?
>
> A lot of those are Perl scripts. I for one don't really want to
> do complicated configuration in bash instead of perl.
Do you thing the kernel config is complicated? Its done basically as
you wuld write the configure scripts for packages.
At first those /usr/sbin/+config scripts are perfectly fine with me,
but later they should be changed to present a uniform configuration
method and not various methods. Without loops rewriting those is
impossible and I won't implement code to handle loops in the parsers
for configure scripts for some time. Also if nobody wants to rewrite
those...
Of cause the scripts can and should remain in the package and the bash
configure scripts should tell you to use them for a full configuration
or as an alternative or the interface should include a
line/button/<some other gui thing> that starts those scripts.
I will introduce a variable like "CONFIG_ALTERNATIVE" to be set in the
configure.variables file if an alternative config program is
present. Setting "CONFIG_ALTERNATIVE=/usr/sbin/fooconfig" or similar
would then add the option to call the alternative script.
May the Source be with you.
Goswin
Reply to: