GNU bug report logs - #23037
avoid issues if CP, MV or RM are predefined in the execution environment

Previous Next

Package: libtool;

Reported by: Richard PALO <richard.palo <at> free.fr>

Date: Thu, 17 Mar 2016 05:47:01 UTC

Severity: normal

To reply to this bug, email your comments to 23037 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-libtool <at> gnu.org:
bug#23037; Package libtool. (Thu, 17 Mar 2016 05:47:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Richard PALO <richard.palo <at> free.fr>:
New bug report received and forwarded. Copy sent to bug-libtool <at> gnu.org. (Thu, 17 Mar 2016 05:47:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Richard PALO <richard.palo <at> free.fr>
To: bug-libtool <at> gnu.org
Subject: avoid issues if CP,
 MV or RM are predefined in the execution environment
Date: Thu, 17 Mar 2016 06:46:37 +0100
Please see problem report and submitted patches https://savannah.gnu.org/support/index.php?108987
It would be great if these could be included in the upcoming release.

Currently, and since many years, pkgsrc has patched libtool to simply 'unset' CP, MV & RM

This patchset 'fixes' the use as documented, that is to respect the environment if these variables
are set, but naturally -- if set -- they will be just the path to the tool and as such can in no
way expect that '-f' is specified (which is '--force' under the Gnu flavours of these tools).
-- 
Richard PALO





This bug report was last modified 9 years and 150 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.