Skip Menu |

This queue is for tickets about the DBD-CSV CPAN distribution.

Report information
The Basics
Id: 69320
Status: resolved
Priority: 0/
Queue: DBD-CSV

People
Owner: Nobody in particular
Requestors: kevin_frost [...] symantec.com
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 0.25
Fixed in: 0.32



Subject: Hard-coded (and nonstandard) Perl path in DBD/CSV.pm
Date: Wed, 6 Jul 2011 23:45:16 +0200
To: <bug-DBD-CSV [...] rt.cpan.org>
From: Kevin Frost <Kevin_Frost [...] symantec.com>
Greetings. In DBD::CSV 0.31, the file CSV.pm is built with the following line at the top: #!/pro/bin/perl I assume that's just an oversight that didn't get caught because it won't cause any problem when you "use" the module. However, it causes problems with automatic requirement generators such as those used to build RPM's for RedHat and related Linux distributions. Also of course if you really want to use a path to Perl, it would be better to ask Perl what the path to it is. :-) The build system in question is Red Hat Enterprise Linux 5 with Perl 5.12.1 (built from source, not system Perl). cheers -- kf.
Subject: Re: [rt.cpan.org #69320] Hard-coded (and nonstandard) Perl path in DBD/CSV.pm
Date: Thu, 7 Jul 2011 07:48:21 +0200
To: bug-DBD-CSV [...] rt.cpan.org
From: "H.Merijn Brand" <h.m.brand [...] xs4all.nl>
On Wed, 6 Jul 2011 17:45:35 -0400, "Kevin Frost via RT" <bug-DBD-CSV@rt.cpan.org> wrote: Show quoted text
> In DBD::CSV 0.31, the file CSV.pm is built with the following line at > the top: > > #!/pro/bin/perl > > I assume that's just an oversight that didn't get caught because it > won't cause any problem when you "use" the module.
It's not an oversight. It is deliberate and I use it automatically in all my perl scripts and modules, as I never use the system perl for any work at all. I always use my own: /pro/bin/perl Show quoted text
> However, it causes problems with automatic requirement generators > such as those used to build RPM's for RedHat and related Linux > distributions.
I'll change it to /usr/bin/perl I know that OpenSUSE includes patches with their distributions to alter this also. I've never seen a problem with this, as a module file is never called on itself. Neither in actual use, nor in the build and test phase. Show quoted text
> Also of course if you really want to use a path to Perl, it would be > better to ask Perl what the path to it is. :-)
As it is absolutely unused by anyone but me, it doesn't matter whatsoever what path is put in there Show quoted text
> The build system in question is Red Hat Enterprise Linux 5 with Perl > 5.12.1 (built from source, not system Perl).
I test most of my modules with about every version released and supported. Currently I have over 80 perl builds. It passes on all versions that are supported. Show quoted text
> cheers > > -- kf.
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using 5.00307 through 5.14 and porting perl5.15.x on HP-UX 10.20, 11.00, 11.11, 11.23 and 11.31, OpenSuSE 10.1, 11.0 .. 11.4 and AIX 5.2 and 5.3. http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Subject: Re: [rt.cpan.org #69320] Hard-coded (and nonstandard) Perl path in DBD/CSV.pm
Date: Thu, 7 Jul 2011 08:31:24 +0200
To: bug-DBD-CSV [...] rt.cpan.org
From: "H.Merijn Brand" <h.m.brand [...] xs4all.nl>
On Wed, 6 Jul 2011 17:45:35 -0400, "Kevin Frost via RT" <bug-DBD-CSV@rt.cpan.org> wrote: Show quoted text
> In DBD::CSV 0.31, the file CSV.pm is built with the following line at the top: > > #!/pro/bin/perl
Actually, I already backported that from what OpenSUSE did See http://repo.or.cz/w/DBD-CSV.git/commit/57e125639d6f308 So it will be in the next release -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using 5.00307 through 5.14 and porting perl5.15.x on HP-UX 10.20, 11.00, 11.11, 11.23 and 11.31, OpenSuSE 10.1, 11.0 .. 11.4 and AIX 5.2 and 5.3. http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Subject: Re: [rt.cpan.org #69320] Hard-coded (and nonstandard) Perl path in DBD/CSV.pm
Date: Thu, 7 Jul 2011 13:13:33 +0200
To: "bug-DBD-CSV [...] rt.cpan.org" <bug-DBD-CSV [...] rt.cpan.org>
From: Kevin Frost <Kevin_Frost [...] symantec.com>
I stand corrected on the oversight assumption. If you don't agree it's a bug just mark it invalid with your explanation; I can see the logic that it's harmless when used by Perl. I didn't mean to imply that you have some responsibility to make rpmbuild happy, just that you might want to prevent others from stumbling over the same issue in the future. If you prefer to require that people use patches that's a perfectly reasonable position, just not one I'd expected. I don't think there's any difference between setting the line to /usr/bin/perl, /pro/bin/perl, or /anything/you/like, since any of these may or may not be present on the build system. I apologize for using the word "nonstandard" which implied I saw a difference. Anyway, it's not unused by everyone but you, because I just used it, even if not in the manner intended. :-) I don't mind if you kill the bug, I would have filed it as "trivial" or "favor to RedHat RPM builders" if I could have. cheers -- kf. On Jul 7, 2011, at 7:48 AM, h.m.brand@xs4all.nl via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=69320 > > > On Wed, 6 Jul 2011 17:45:35 -0400, "Kevin Frost via RT" > <bug-DBD-CSV@rt.cpan.org> wrote: >
>> In DBD::CSV 0.31, the file CSV.pm is built with the following line at >> the top: >> >> #!/pro/bin/perl >> >> I assume that's just an oversight that didn't get caught because it >> won't cause any problem when you "use" the module.
> > It's not an oversight. It is deliberate and I use it automatically in > all my perl scripts and modules, as I never use the system perl for any > work at all. I always use my own: /pro/bin/perl >
>> However, it causes problems with automatic requirement generators >> such as those used to build RPM's for RedHat and related Linux >> distributions.
> > I'll change it to /usr/bin/perl > > I know that OpenSUSE includes patches with their distributions to alter > this also. I've never seen a problem with this, as a module file is > never called on itself. Neither in actual use, nor in the build and > test phase. >
>> Also of course if you really want to use a path to Perl, it would be >> better to ask Perl what the path to it is. :-)
> > As it is absolutely unused by anyone but me, it doesn't matter > whatsoever what path is put in there >
>> The build system in question is Red Hat Enterprise Linux 5 with Perl >> 5.12.1 (built from source, not system Perl).
> > I test most of my modules with about every version released and > supported. Currently I have over 80 perl builds. It passes on all > versions that are supported. >
>> cheers >> >> -- kf.
> > -- > H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ > using 5.00307 through 5.14 and porting perl5.15.x on HP-UX 10.20, 11.00, > 11.11, 11.23 and 11.31, OpenSuSE 10.1, 11.0 .. 11.4 and AIX 5.2 and 5.3. > http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ > http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/ >
Subject: Re: [rt.cpan.org #69320] Hard-coded (and nonstandard) Perl path in DBD/CSV.pm
Date: Thu, 7 Jul 2011 13:35:37 +0200
To: bug-DBD-CSV [...] rt.cpan.org
From: "H.Merijn Brand" <h.m.brand [...] xs4all.nl>
On Thu, 7 Jul 2011 07:13:54 -0400, "Kevin Frost via RT" <bug-DBD-CSV@rt.cpan.org> wrote: Show quoted text
> I stand corrected on the oversight assumption. > > If you don't agree it's a bug just mark it invalid with your explanation; > I can see the logic that it's harmless when used by Perl. > > I didn't mean to imply that you have some responsibility to make rpmbuild > happy, just that you might want to prevent others from stumbling over > the same issue in the future.
As I already replied in another mail, I already committed that change in the git repository based on the same patch that OpenSUSE did to this module. SO it is clear that I don't disapprove of the change. I disapprove of the reasoning you came with to motivate me to make that change. Show quoted text
> If you prefer to require that people use patches that's a perfectly > reasonable position, just not one I'd expected. > > I don't think there's any difference between setting the line to > /usr/bin/perl, /pro/bin/perl, or /anything/you/like, since any of > these may or may not be present on the build system.
There *is* a difference. For me. The rest of the world won't ever see the difference. I quite often make a module an executable, so I can then test inside functionality from the command prompt without the need of a complete working environment. Before I commit, I remove that testing code, so you won't ever see that. Example, at the end of (a random) module: --8<--- # Try a basic Command Line Interface. Way open for improvements unless (caller) { use Data::Peek; my $user = getpwuid $<; my $rv = InternalMethod (undef, @ARGV); DDumper { in => \@ARGV, out => $rv }; exit 0; } 1; Show quoted text
> I apologize for using the word "nonstandard" which implied I saw > a difference.
No need for apologies. Show quoted text
> Anyway, it's not unused by everyone but you, because I just used > it, even if not in the manner intended. :-)
Please post/mail me (preferably not through RT) any changes Redhat applies to my modules and I will seriously look into them. Show quoted text
> I don't mind if you kill the bug, I would have filed it as > "trivial" or "favor to RedHat RPM builders" if I could have.
I won't Show quoted text
> cheers > -- kf.
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using 5.00307 through 5.14 and porting perl5.15.x on HP-UX 10.20, 11.00, 11.11, 11.23 and 11.31, OpenSuSE 10.1, 11.0 .. 11.4 and AIX 5.2 and 5.3. http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/