Bug#869994: proposed fix

2018-01-09 Thread Stephen Schmiechen
Yeah I tend to run several customised instances in lots of locations so
FindBin is less fragile for me and works most like the 'dot' did.
So hopefully it saves someone some time.
Cheers
--turtle

On Mon, Jan 8, 2018 at 12:24 PM, Robert J. Clay  wrote:

> > Greetings all using FindBin and adding the current directory everywhere
> > sql-ledger calls perl should fix the issue in all versions.
>
>I appreciate the example perl script you provided but since it's
> known where the package is installing sql-ledger to, I don't think
> using "FindBin" is necessary.  At least, that's what what I'm assuming
> with the patch I've created for the ITA[1] I've been working on.  I
> originally wrote the patch against sql-ledger 3.0.8 but will be
> updating as necessary for use against the most recent version I
> currently see, which is 3.2.6.
>
>
> --
> Robert J. Clay
> rjc...@gmail.com
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862963
>


Bug#869994: proposed fix

2018-01-06 Thread Stephen Schmiechen
Greetings all using FindBin and adding the current directory everywhere
sql-ledger calls perl should fix the issue in all versions.
An example perl script would be:

perl -0777 -i.original -pe 's/(#!\/usr\/bin\/perl)/$1\n#perl 5.25 Fix:\nuse
FindBin qw\(\$Bin\);\nuse lib \"\$Bin\"\;/igs' *.pl

Cheers
Turtle