Skip Menu |
 

This queue is for tickets about the Config-Std CPAN distribution.

Report information
The Basics
Id: 42135
Status: open
Priority: 0/
Queue: Config-Std

People
Owner: Nobody in particular
Requestors: mm [...] elabnet.de
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



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>
Download (untitled) / with headers
text/plain 394b
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
Download (untitled) / with headers
text/plain 770b
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


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.