Hi Joey > > First, I took a stab at implementing debconf-get-selections, see patch > > attached. It seems to work, but any feedback would be very welcome. I > > added entries to cdebconf.conf-dist for the --installer option, which I > > hope is the correct way. > > That's probably a good clean way to do it. I hope that cdebconf does not > try to use those stanzas in normal operation, /var/log/installer may not > always exist.
I guess the alternative would be to have a separate conf file in /usr/lib/cdebconf that would only contain the installer db info. > > I also had a look at Colin's patch, found a bug in debconf-escape, and > > hope to send a working patch very soon. A pointer to test the escape > > CAPB would be welcome as well, as I started work on it, based on the > > Colin's patch. > > Doing a SUBST of something\nwith\nnewlines and checking it is > displayed as mutiple lines would be a good test. There are > few packages that use it, and probably mostly for error display. Ok, will have a look, thanks. > > Obviously any comment, feedback, or pointer to ways I could help would > > be very welcome. > > The other blocking bugs of #328498 are of course relevant. The key thing > is the template autoloading stuff and general tweaks so cdebconf can be > used when installing packages. I already have #328498 on my radar, thanks. I'll try to keep with this bug for now, it seems a very good entry point to start learning about the cdebconf internals and interfaces ; but will have a look at the others as well. Last question, how would you like me to provide patche(s) ? Is one for each utility ok ? Regis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org