On Sat, May 23, 2009 at 06:05:11AM -0700, Ryan Niebur wrote:
> I can reproduce this. Of course, this debian/rules triggers the
> lintian warning debian-rules-uses-pwd, but from what Carl says this
> causes other problems, and the fix for this shouldn't hurt anything.

Obviously I misunderstood the bug report until now. Sorry.

> [...]
>  debian/rules build
> PWD is: /home/ryan52/pkg-perl/trunk/libtest-file-perl
> CURDIR is: 
> /server/home/ryan52/pkg-perl/trunk/build-area/libtest-file-perl-1.27
> false
> make: *** [build] Error 1
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
> 
> after applying the attached patch, these are my results (as expected):
> PWD is: /server/home/ryan52/pkg-perl/trunk/build-area/libtest-file-perl-1.27
> CURDIR is: 
> /server/home/ryan52/pkg-perl/trunk/build-area/libtest-file-perl-1.27
> 
> may I commit this patch (after updating the changelog, of course)?

TBH I don't really get why a chdir wouldn't update the current working
directory of the environment but I assume this is because chdir works
within the script while ENV{PWD} reflects the directory outside the
script.

I can't see any side effects but I'm not entirely sure. Neil? Eddy?

Hauke

Attachment: signature.asc
Description: Digital signature

Reply via email to