Eric Van Buggenhaut <[EMAIL PROTECTED]> writes:
> The upstream code requires the administrator to introduce the user
> data (username, password, port, database, etc.) in the same Password.pm file,
> which looks horrible to me.
Ok, we've seen some solutions but the real problem remains: The perl
m
On Fri, Dec 28, 2001 at 11:16:03AM -0600, Colin Watson wrote:
> On Fri, Dec 28, 2001 at 03:02:29PM +0100, Eric Van Buggenhaut wrote:
> > my %virtual1 = {};
> [...]
> > $virtual1->{$user[0]}->{$fields[$_]} = $user[$_];
> [...]
> > When running the script using this module, I get this
On Sat, Dec 29, 2001 at 03:53:19PM +1100, Craig Sanders wrote:
> On Fri, Dec 28, 2001 at 01:11:15PM +0100, Eric Van Buggenhaut wrote:
> > print Dumper($virtula1);
> >
[...]
> which is pretty much the structure you wanted.
>
>
>
> other comments:
>
> i still think you should use a field s
On Fri, Dec 28, 2001 at 01:11:15PM +0100, Eric Van Buggenhaut wrote:
> print Dumper($virtula1);
>
> I spent some time try to understand why it was failing ;)
oops. yeah. i should have cut-and-pasted the script i got working in
/tmp instead of what i originally typed in the message. there
On Fri, Dec 28, 2001 at 03:02:29PM +0100, Eric Van Buggenhaut wrote:
> my %virtual1 = {};
[...]
> $virtual1->{$user[0]}->{$fields[$_]} = $user[$_];
[...]
> When running the script using this module, I get this error:
>
> mrmime_SLASH:/# install-slashsite
> Global symbol "$virtual1"
On Fri, Dec 28, 2001 at 10:31:01AM +1100, Craig Sanders wrote:
> On Thu, Dec 27, 2001 at 07:03:38PM +0100, Eric Van Buggenhaut wrote:
[...]
>
> you can verify that this does what you want by using the Data::Dumper
> module. e.g. by adding something like the following lines to the script:
>
>
On Thu, Dec 27, 2001 at 10:53:24AM -0500, [EMAIL PROTECTED] wrote:
> On Thu, Dec 27, 2001 at 11:49:12PM +0800, James Bromberger wrote:
> > On Thu, Dec 27, 2001 at 09:19:16AM -0600, Steve Langasek wrote:
> >
> > > My own approach? Write your own parser for a simple 'key = value' style
> > > confi
On Fri, Dec 28, 2001 at 10:31:01AM +1100, Craig Sanders wrote:
> On Thu, Dec 27, 2001 at 07:03:38PM +0100, Eric Van Buggenhaut wrote:
[...]
>
> my %virtual1 = {};
>
> while (<>) {
> chomp ;
> s/#.*//; # strip comments
> s/^\s*|\s*$//g; # stri
I demand that Eric Van Buggenhaut may or may not have written...
> On Thu, Dec 27, 2001 at 09:19:16AM -0600, Steve Langasek wrote:
[snip]
> #!/usr/bin/perl -w
> #open (IN,"/etc/dbix-password.conf");
> open (IN,"dbix-password.conf");
> while () {
> next if (/^#/ || /^$/);
> @host
On Thu, Dec 27, 2001 at 07:03:38PM +0100, Eric Van Buggenhaut wrote:
> I wanted to be able to use a config file similar to /etc/passwd like:
>
> #This is the list of users needed by DBIx::Password
> #(/usr/lib/perl5/DBIx/Password.pm)
> #
> #Syntax is:
> #host:username:password:port:database:attrib
On Thu, Dec 27, 2001 at 09:19:16AM -0600, Steve Langasek wrote:
> On Thu, Dec 27, 2001 at 02:18:15PM +0100, Eric Van Buggenhaut wrote:
> > Hi,
>
> > I'm currently packaging libdbix-password-perl.
>
> > The upstream code requires the administrator to introduce the user
> > data (username, password
On Thu, Dec 27, 2001 at 09:19:16AM -0600, Steve Langasek wrote:
> My own approach? Write your own parser for a simple 'key = value' style
> config file. This can usually be done in ten lines or less[1] using
> perl's powerful regexp engine.
Why not just 'apt-get install libappconfig-perl', then
On Thu, Dec 27, 2001 at 11:49:12PM +0800, James Bromberger wrote:
> On Thu, Dec 27, 2001 at 09:19:16AM -0600, Steve Langasek wrote:
>
> > My own approach? Write your own parser for a simple 'key = value' style
> > config file. This can usually be done in ten lines or less[1] using
> > perl's po
On Thu, Dec 27, 2001 at 09:19:16AM -0600, Steve Langasek wrote:
> My own approach? Write your own parser for a simple 'key = value' style
> config file. This can usually be done in ten lines or less[1] using
> perl's powerful regexp engine.
> [1] depending, of course, on your standards for co
On Thu, Dec 27, 2001 at 02:18:15PM +0100, Eric Van Buggenhaut wrote:
> Hi,
> I'm currently packaging libdbix-password-perl.
> The upstream code requires the administrator to introduce the user
> data (username, password, port, database, etc.) in the same Password.pm file,
> which looks horrible t
Hi,
I'm currently packaging libdbix-password-perl.
The upstream code requires the administrator to introduce the user
data (username, password, port, database, etc.) in the same Password.pm file,
which looks horrible to me.
So my idea is to create a config file in /etc sourced by the module. I
h
16 matches
Mail list logo
