Re: toolchain/48534: bogus file names in source tree

[Alistair Crooks <agc%pkgsrc.org@localhost>]

The following reply was made to PR toolchain/48534; it has been noted by GNATS.

From: Alistair Crooks <agc%pkgsrc.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: toolchain-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost, martin%netbsd.org@localhost
Subject: Re: toolchain/48534: bogus file names in source tree
Date: Sun, 26 Jan 2014 05:16:35 +0100

 On Sun, Jan 26, 2014 at 03:55:01AM +0000, Aleksej Saushev wrote:
 >  > On Sat, Jan 25, 2014 at 08:03:26AM +0400, Aleksej Saushev wrote:
 >  >> I think that the source code management system and regular maintainance
 >  >> scripts ought to be fixed instead.
 >  >
 >  > Neither the source code management nor any regular maintaninance scripts
 >  > run on TNF machines have any problems with the files in question. There
 >  > is nothing to fix here.
 >  >
 >  > However: besides the ones in llvm we have no files with spaces in
 >  > the repository. This simplifies a lot of ad-hoc tasks for developers
 >  > (like find . -name ... | xargs rm), which in general need a lot of 
 > thinking,
 >  > testing or use of other/more complex tools.
 >  >
 >  > Giving this up for no good reason is just very lame.
 >  
 >  No, it is not lame in any way. It is important to learn working with
 >  such files in ad hoc tasks. In particular, we should learn to avoid
 >  habits of using broken tools like xargs. If we need to improve tools
 >  in order to achieve that, we ought to improve them rather than run away
 >  from it. You don't help to improve anything if you force everyone to
 >  stick to old conventions that support old habits.
 
 Aleksej, there is a reason find(1) has a -print0 clause, and xargs(1)
 has a -0 argument.
 
 Martin's right, we should keep these tests.
 
 Regards,
 Alistair