Bug #42135 for Config-Std: Whitespaces around separator / option to suppress

Sun Jan 04 12:34:25 2009 mm [...] elabnet.de - Ticket created

Subject:	Whitespaces around separator
Date:	Sun, 4 Jan 2009 18:34:05 +0100
To:	<bug-Config-Std [...] rt.cpan.org>
From:	"Michael Markstaller" <mm [...] elabnet.de>

Hi, using Config::Std for several things, I encountered one problem: When values are written, there's always a whitespace before and after the separator (=) inserted. This is unfortunately problematic when using with shell-fragments (like /etc/default/* on Debian).. Is there an easy way to change this behavior ? I'm not enough perl-guru to find it in the pm myself.. best regards Michael

Sun Mar 07 13:59:33 2010 BRICKER [...] cpan.org - Subject changed from 'Whitespaces around separator' to 'Whitespaces around separator / option to suppress'

Sun Mar 07 13:59:33 2010 BRICKER [...] cpan.org - Status changed from 'new' to 'open'

Sun Mar 07 13:59:33 2010 BRICKER [...] cpan.org - Severity Wishlist added

Sun Mar 07 14:04:48 2010 BRICKER [...] cpan.org - Correspondence added

On Sun Jan 04 12:34:25 2009, mm@elabnet.de wrote: Show quoted text

> Hi, > > using Config::Std for several things, I encountered one problem: > When values are written, there's always a whitespace before and after > the separator (=) inserted. > This is unfortunately problematic when using with shell-fragments > (like /etc/default/* on Debian).. > > Is there an easy way to change this behavior ? I'm not enough perl- > guru to find it in the pm myself.. >

Shell fragments are outside the intended use of the config module, but Debian is a sufficiently interesting use case I am marking this a with-list item. A Shell-frag subclass may be the right way to leverage Config::Std round-trip ability with a subtly different syntax for Shell. Bill new Co-Maintainer / cleaning RT queue