Module regression

[Phil Dobbin]

I need to step back a version in a module compliled from source (from v.3.0 - 
v.2.0).

What's the best way to go about this (again compiling from source rather than 
cpan)?

Thanks,

Regards,

Phil.

Re: Module regression

[Ken Williams]

On Nov 16, 2004, at 3:47 PM, Phil Dobbin wrote:
I need to step back a version in a module compliled from source (from 
v.3.0 - v.2.0).

What's the best way to go about this (again compiling from source 
rather than cpan)?
* The best way to do this is to have a backup of the previous system 
with v.2.0 installed, and revert to the backup.

* If you don't have a backup, the next best way is to use a package 
manager like RPM or DPKG to track your installed modules, remove the 
v.3.0 package and install the v.2.0 package.

* If you don't have a backup, and you don't have a package manager, the 
next next best way is to go back in time and start using one or the 
other.

* If you can't do any of the above, your only option is to brute-force 
remove v.3.0 using the packlist file (CPANPLUS provides some support 
for this) and then install v.2.0 again.  This is not a great option 
because packlists can get out of sync, it can remove files that are 
required for some other thing you've installed, and so on.

Incidentally, using CPAN *is* compiling from source.
 -Ken

Perl Win32 vs. OS X

[Bruce Pascal]

All,

I am having a problem with a parser which works in DOS, but does not work in
the OS X BSD shell. The problem is trying to find lines that begin with a
newline character. I have tried exactly the same source files, but it
doesn¹t work. Here¹s the code:

if ($line =~ /^\n/) {
   # Do Something
}

Why would this happen? Any ideas?

-Bruce

Re: Perl Win32 vs. OS X

[Bruce Pascal]

Dave,

Thanks a bunch for the help - it worked. I had to change the line to
if ($line =~ /^\r\n?/) { etc ...
To catch the empty lines.

Best,
Bruce


On 11/16/04 10:34 PM, Dave Gomez [EMAIL PROTECTED] wrote:

 Bruce,
   depending on the platform of the originating text file, and in OSX that
 covers 2 bases really, the newline character is different.
 
 Moc OS9  below = \r
 Unix = \n
 Dos = \n\r
 OSX = \n but many text files are still \r from legacy
 
 So, to make you code good all around, try this instead
 
 if ($line =~ /^\n|\r\n?/) {
 # Do Something
 }
  
 
 Dave
 
 On 11/16/04 7:53 PM, Bruce Pascal [EMAIL PROTECTED] wrote:
 
 All,
 
 I am having a problem with a parser which works in DOS, but does not work in
 the OS X BSD shell. The problem is trying to find lines that begin with a
 newline character. I have tried exactly the same source files, but it
 doesn¹t work. Here¹s the code:
 
 if ($line =~ /^\n/) {
# Do Something
 }
 
 Why would this happen? Any ideas?
 
 -Bruce