Sat Oct 06 07:15:20 2012: Request 80026 was acted upon.
Transaction: Correspondence added by m...@jodyclements.com
Queue: Inline
Subject: Re: [rt.cpan.org #80026] LIB is being in correctly quoted when
using more than one lib path
Broken in: 0.48, 0.48_01, 0.48_02, 0.49, 0.49_01, 0.49_02, 0.50, 0.50_01,
0.50_02
Severity: Important
Owner: Nobody
Requestors: jcleme...@cpan.org
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=80026 >
On Oct 5, 2012, at 21:56, "Sisyphus via RT" <bug-inl...@rt.cpan.org> wrote:
> <URL: https://rt.cpan.org/Ticket/Display.html?id=80026 >
>
> On Fri Oct 05 11:23:15 2012, JCLEMENTS wrote:
>
>> I looked into the source and it looks like the quote_space subroutine
>> (C.pm line 84) is quoting the entire INC
>> line("-I/opt/src/Bio-HMM-Logo-0.01/src/src
>> -I/opt/src/Bio-HMM-Logo-0.01/src/easel") if I have more than one path.
>
> Thanks for the report, Jody.
> I take it that if, in line 84, you replace "quote_space($value)" with
> "$value", then everything is ok with 0.50 ?
That is correct.
>
> The point of quote_space() was to (help) accommodate those who want to
> put things in directories whose names contain white space (eg C:/Program
> Files/).
> It's a very poor situation, indeed, that in trying to accommodate insane
> (and irritating) behaviour, a completely sane practice has been broken -
> and I'll release a new version of Inline once I decide how to fix this.
>
> I guess quote_space() needs to be able to distinguish between (insane)
> spaces that are part of a directory name, and (sane) spaces that act as
> a path separator ... but I haven't yet looked closely at this.
>
I totally understand your pain. If I can think of a way to fix it I will get
back to you. Thanks for the response.
Regards,
Jody
