Note also that the *shell* issue is hard because it's hardcoded into
scripts in various ways, so you really need /bin/sh to work whatever
it is -- the use of cp, however, can be dealt with by adding
/usr/gnu/bin to your path :-)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word
On Fri, 12 Dec 1997, Oliver Elphick wrote:
So use this, which should work on any Unix anywhere:
cd source; find . -print | cpio -pdm target
But then the package would have to pre-depend on cpio, which isn't even a
`required' or `essential' package. I think this is a bad thing to use in
a
On 11 Dec 1997, Douglas Bates wrote:
I have a vague recollection of seeing some comments regarding flags
for cp that should be avoided in packaging scripts. Perhaps this was
in the discussion of bashisms.
I don't remember anything like that. Debian ships with `GNU cp', so I
don't see a
Christian Schwarz [EMAIL PROTECTED] writes:
On 11 Dec 1997, Douglas Bates wrote:
I have a vague recollection of seeing some comments regarding flags
for cp that should be avoided in packaging scripts. Perhaps this was
in the discussion of bashisms.
I don't remember anything like
Douglas Bates wrote:
Christian Schwarz [EMAIL PROTECTED] writes:
On 11 Dec 1997, Douglas Bates wrote:
I have a vague recollection of seeing some comments regarding flags
for cp that should be avoided in packaging scripts. Perhaps this was
in the discussion of bashisms.
Douglas Bates [EMAIL PROTECTED] writes:
But consider the recent discussion of porting dpkg to other systems.
If you were using dpkg on Solaris or HP-UX or ... you may not be
able to count on cp understanding the -a flag.
Fooblah. Debian is about systems integration; GNU fileutils is an
6 matches
Mail list logo
