Re: Moving/Deleting open files isn't portable

2000-03-21 Thread Thomas Bushnell, BSG
Earnie Boyd <[EMAIL PROTECTED]> writes: > Haven't thought of one yet. But whatever the fix entails it will > have to close the fd to foo before the mv/rm. In that case, Win-32 is not Posix compliant, and it should not be a significant priority of the GNU Project to support it.

Re: Moving/Deleting open files isn't portable

2000-03-21 Thread Thomas Bushnell, BSG
Earnie Boyd <[EMAIL PROTECTED]> writes: > Sorry, sent too soon. Also, GNU's Not Unix, and the intent of autoconf is > software portability. Indeed, and I don't mind people putting patches in to deal. But my tests don't worry about it, and I don't want GNU maintainers to think they have an obli

Re: FHS

2002-01-05 Thread Thomas Bushnell, BSG
"Richard B. Kreckel" <[EMAIL PROTECTED]> writes: > Now four years into FHS-2.0, can we consider this a bug? Or is FHS buggy? FHS is buggy, but (as the primary engine behind the makefile standards in this area) I think it's time to give in, and move mandir and infodir into the share hierarchy.

Re: FHS

2002-01-05 Thread Thomas Bushnell, BSG
Guido Draheim <[EMAIL PROTECTED]> writes: > Didn't we had a lengthy talk about it lately? So since I'm the main directories for the GNU Coding Standards, I've sent a note to RMS requesting that he alter the coding standards to change the placement of infodir and mandir to put them under datadir

Re: FHS

2002-01-05 Thread Thomas Bushnell, BSG
Harlan Stenn <[EMAIL PROTECTED]> writes: > Except that datadir is for read-only architecture-independent data, and man > pages are not architecture-independent. Granted, it is possible to > reorganize the subdirs into arch-specific subdirs, but that is not presently > the case. Also, different

Re: FHS

2002-01-05 Thread Thomas Bushnell, BSG
Harlan Stenn <[EMAIL PROTECTED]> writes: > There is more to software than GNU. Sure, but the GNU Coding Standards are for GNU, by definition. There are many things that are disallowed by them in the interests of making GNU better. For example, info files must all be machine independent. There

Re: FHS

2002-01-06 Thread Thomas Bushnell, BSG
Russ Allbery <[EMAIL PROTECTED]> writes: > Personally, I'm somewhat annoyed to see yet more paths going into Autoconf > that I'll then have to override to get the installation paths that I want > (namely a flat tree of bin, sbin, lib, man, info, and etc); with over five > hundred packages install

Re: FHS

2002-01-06 Thread Thomas Bushnell, BSG
Harlan Stenn <[EMAIL PROTECTED]> writes: > > The changes here for the GNU Coding Standards (which I'm proposing, > > and RMS has now agreed to) will not add any new paths, it will simply > > change some that currently exist. > > For this to be effective and useful, it would mean that most every

Re: FHS

2002-01-06 Thread Thomas Bushnell, BSG
Bruce Korb <[EMAIL PROTECTED]> writes: > "Thomas Bushnell, BSG" wrote: > > > > Harlan Stenn <[EMAIL PROTECTED]> writes: > > > > > > The changes here for the GNU Coding Standards (which I'm proposing, > > > > and RMS has

Re: FHS

2002-01-06 Thread Thomas Bushnell, BSG
Russ Allbery <[EMAIL PROTECTED]> writes: > Bruce Korb <[EMAIL PROTECTED]> writes: > > > AutoConf should support very convenient mechanisms to handle whatever > > layout makes sysadmins happy. --with-gnu-layout or --with-fhs-layout > > would be good. Maybe better: --with-layout-file=/path/to/l