Re: fetching module version from the command line

2006-07-17 Thread demerphq
On 7/17/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: * Graham Barr <[EMAIL PROTECTED]> [2006-07-17 02:00]: > perl -MDBI\ 999 > DBI version 999 required--this is only version 1.50. > BEGIN failed--compilation aborted. You can use an equals sign instead of a space, there, which makes it a little ea

Re: fetching module version from the command line

2006-07-16 Thread Andreas J. Koenig
> On Mon, 17 Jul 2006 02:24:37 +0200, "A. Pagaltzis" <[EMAIL PROTECTED]> > said: > * Graham Barr <[EMAIL PROTECTED]> [2006-07-17 02:00]: >> perl -MDBI\ 999 >> DBI version 999 required--this is only version 1.50. >> BEGIN failed--compilation aborted. > You can use an equals sign in

Re: fetching module version from the command line

2006-07-16 Thread A. Pagaltzis
* Graham Barr <[EMAIL PROTECTED]> [2006-07-17 02:00]: > perl -MDBI\ 999 > DBI version 999 required--this is only version 1.50. > BEGIN failed--compilation aborted. You can use an equals sign instead of a space, there, which makes it a little easier to type: perl -MDBI=666 -e1 Regards, -- #A

Re: fetching module version from the command line

2006-07-16 Thread Graham Barr
David Wheeler wrote: > On Jul 12, 2006, at 03:41, Gabor Szabo wrote: > >> perl -MModule -e'print $Module::VERSION' > > I have this alias set up: > > function pv () { perl -M$1 -le "print $1->VERSION"; } > > I think that calling ->VERSION is more correct. I am sure this discussion has happene

Re: fetching module version from the command line

2006-07-13 Thread Andreas J. Koenig
> On Thu, 13 Jul 2006 19:36:52 -0400, "Randy W. Sims" <[EMAIL PROTECTED]> > said: > David Wheeler wrote: >> On Jul 13, 2006, at 05:56, Fergal Daly wrote: >> >>> That's funny, it looks like I did put some code in to disable the END >>> block if it's "require"d rather than "use"d. Tu

Re: fetching module version from the command line

2006-07-13 Thread Randy W. Sims
David Wheeler wrote: On Jul 13, 2006, at 05:56, Fergal Daly wrote: That's funny, it looks like I did put some code in to disable the END block if it's "require"d rather than "use"d. Turns out I did this to make MakeMaker happy, so MakeMaker does actually do a full require, Well, IIRC, both Ma

Re: fetching module version from the command line

2006-07-13 Thread Yitzchak Scott-Thoennes
On Thu, Jul 13, 2006 at 02:29:38PM +0300, Gabor Szabo wrote: > On 7/13/06, Fergal Daly <[EMAIL PROTECTED]> wrote: > >I could change it so that it tries to figure out whether it's being > >used for real or not and disable the END block code but that's stress > >and hassle. As a module author, as far

Re: fetching module version from the command line

2006-07-13 Thread David Wheeler
On Jul 13, 2006, at 05:56, Fergal Daly wrote: That's funny, it looks like I did put some code in to disable the END block if it's "require"d rather than "use"d. Turns out I did this to make MakeMaker happy, so MakeMaker does actually do a full require, Well, IIRC, both MakeMaker and Module::Bu

Re: fetching module version from the command line

2006-07-13 Thread Fergal Daly
On 13/07/06, Smylers <[EMAIL PROTECTED]> wrote: Fergal Daly writes: > On 12/07/06, Smylers <[EMAIL PROTECTED]> wrote: > > > I have this one-liner as ~/bin/pmv: > > > > #! /bin/sh > > perl -m$1 -le 'print '$1'->VERSION || die "No VERSION in '$1'\n"' > > These all fail for modules that do interest

Re: fetching module version from the command line

2006-07-13 Thread Smylers
Fergal Daly writes: > On 12/07/06, Smylers <[EMAIL PROTECTED]> wrote: > > > I have this one-liner as ~/bin/pmv: > > > > #! /bin/sh > > perl -m$1 -le 'print '$1'->VERSION || die "No VERSION in '$1'\n"' > > These all fail for modules that do interesting things. For example > Test::NoWarnings perf

Re: fetching module version from the command line

2006-07-13 Thread H.Merijn Brand
On Thu, 13 Jul 2006 14:29:38 +0300, "Gabor Szabo" <[EMAIL PROTECTED]> wrote: > On 7/13/06, Fergal Daly <[EMAIL PROTECTED]> wrote: > > I could change it so that it tries to figure out whether it's being > > used for real or not and disable the END block code but that's stress > > and hassle. As a m

Re: fetching module version from the command line

2006-07-13 Thread Gabor Szabo
On 7/13/06, Fergal Daly <[EMAIL PROTECTED]> wrote: I could change it so that it tries to figure out whether it's being used for real or not and disable the END block code but that's stress and hassle. As a module author, as far as I'm concerned, if MakeMaker can figure out my version then my job

Re: fetching module version from the command line

2006-07-13 Thread Fergal Daly
On 12/07/06, Smylers <[EMAIL PROTECTED]> wrote: David Wheeler writes: > On Jul 12, 2006, at 03:41, Gabor Szabo wrote: > > >perl -MModule -e'print $Module::VERSION' > > I have this alias set up: > > function pv () { perl -M$1 -le "print $1->VERSION"; } Along similar lines, I have this one-line

Re: fetching module version from the command line

2006-07-13 Thread Smylers
David Wheeler writes: > On Jul 12, 2006, at 03:41, Gabor Szabo wrote: > > >perl -MModule -e'print $Module::VERSION' > > I have this alias set up: > > function pv () { perl -M$1 -le "print $1->VERSION"; } Along similar lines, I have this one-liner as ~/bin/pmv: #! /bin/sh perl -m$1 -le 'prin

Re: fetching module version from the command line

2006-07-12 Thread David Wheeler
On Jul 12, 2006, at 03:41, Gabor Szabo wrote: perl -MModule -e'print $Module::VERSION' I have this alias set up: function pv () { perl -M$1 -le "print $1->VERSION"; } I think that calling ->VERSION is more correct. Best, David

Re: fetching module version from the command line

2006-07-12 Thread H.Merijn Brand
On 12 Jul 2006 11:52:07 -, Rafael Garcia-Suarez <[EMAIL PROTECTED]> wrote: > "Gabor Szabo" wrote in perl.qa : > > While checking if the versions of all the modules are as > > required in our installation I am using the following one liner to > > fetch the version numbers. > > > > perl -MModule

Re: fetching module version from the command line

2006-07-12 Thread Rafael Garcia-Suarez
"Gabor Szabo" wrote in perl.qa : > While checking if the versions of all the modules are as > required in our installation I am using the following one liner to > fetch the version numbers. > > perl -MModule -e'print $Module::VERSION' You should probably use -mModule to avoid calling Module::impor

Re: fetching module version from the command line

2006-07-12 Thread H.Merijn Brand
On Wed, 12 Jul 2006 13:41:16 +0300, "Gabor Szabo" <[EMAIL PROTECTED]> wrote: > While checking if the versions of all the modules are as > required in our installation I am using the following one liner to > fetch the version numbers. > > perl -MModule -e'print $Module::VERSION' Not really reliab

Re: fetching module version from the command line

2006-07-12 Thread Adriano Ferreira
On 7/12/06, Gabor Szabo <[EMAIL PROTECTED]> wrote: While checking if the versions of all the modules are as required in our installation I am using the following one liner to fetch the version numbers. perl -MModule -e'print $Module::VERSION' This one-liner doesn't work all the time in modul

fetching module version from the command line

2006-07-12 Thread Gabor Szabo
While checking if the versions of all the modules are as required in our installation I am using the following one liner to fetch the version numbers. perl -MModule -e'print $Module::VERSION' Some of the modules print extra error messages and some print only error messages. I have sent e-mail to