Quoting Thomas Goirand (2014-10-17 17:47:27)
> On 10/17/2014 04:51 PM, Jonas Smedegaard wrote:
>> Quoting Thomas Goirand (2014-10-17 09:51:04)
>>> On 10/17/2014 01:41 PM, Bas Wijnen wrote:
I don't have a bug tracker yet, but I can upload this to unstable
if people don't complain too much
On 10/17/2014 04:51 PM, Jonas Smedegaard wrote:
> Quoting Thomas Goirand (2014-10-17 09:51:04)
>> On 10/17/2014 01:41 PM, Bas Wijnen wrote:
>>> I don't have a bug tracker yet, but I can upload this to unstable if
>>> people don't complain too much about the code. ;-) Then the bts can
>>> be used
Quoting Thomas Goirand (2014-10-17 09:51:04)
> On 10/17/2014 01:41 PM, Bas Wijnen wrote:
>> I don't have a bug tracker yet, but I can upload this to unstable if
>> people don't complain too much about the code. ;-) Then the bts can
>> be used for feature requests (and bugs of course).
>
> Please
Really, really cool analysis and wor, Bas!
Quoting Bas Wijnen (2014-10-17 07:41:21)
> It's dh-parseconfig:
> http://wijnen.dtdns.net/archive/unstable/{all,source}/dh-parseconfig*
[...]
> I don't have a bug tracker yet, but I can upload this to unstable if
> people don't complain too much about th
On 10/17/2014 01:41 PM, Bas Wijnen wrote:
> Getting random packages from apt-cache rdepends debconf shows:
>
> - several packages that use debconf for questions that are only about
> actions that don't need to be (and aren't) stored in config files.
I previously thought that it was the case. Th
On Thursday 16 October 2014 22:34:15 Bas Wijnen wrote:
> Oh yes, and I have some code ready for feedback. I haven't written the
> script libraries yet (and I want others to write some of them), but I
> have written the debhelper module for using them.
For what it's worth, lcdproc package [1] use
On Fri, Oct 17, 2014 at 12:37:27PM +0800, Thomas Goirand wrote:
> On 10/17/2014 04:34 AM, Bas Wijnen wrote:
> > So debconf needs to read configuration files, but it doesn't know how to
> > parse them. So it does the only thing it can: it uses its cache. Which
> > means that each and every package
On 10/17/2014 04:34 AM, Bas Wijnen wrote:
> So debconf needs to read configuration files, but it doesn't know how to
> parse them. So it does the only thing it can: it uses its cache. Which
> means that each and every package that uses debconf must make sure that
> they read the configuration fil
As I wrote in the blend thread, reading through bug #311188 raised some
new questions for me about this one.
I will start by explaining the original problem again; it seemed to me
that it wasn't understood by everyone. Then I'll add some new thoughts
based on that bug. Finally, I present some co
9 matches
Mail list logo
