Re: [Gnu-arch-users] File naming conventions

[Magnus Therning]

On Mon, Oct 18, 2004 at 02:43:09PM +1000, Zenaan Harkness wrote:
>File naming conventions (or rather, breaking traditional conventions,
>or, creating new conventions) is at least one "barrier to entry" factor
>for potential new arch users.
>
>To get a more objective conversation underway, can we analyze what
>problems exist with arch's conventions, and the seriousness for each
>shell?
>
>Arch file naming conventions graded consternation table
>-------------------------------------------------------
>(sorry, I can't think of a good title right now...):
>
>(someone might be able to separate bash versions too)
>
>0 = neutral, 1 = annoyance, 2 = potential trouble, 3 = serious
>
>FILETYPE  bash  tcsh  csh  cygwin  mingw  w32_native  OSX
>{files}    1     1     1     ?       ?        ?        ?
>+files     1     1     1     ?       ?        ?        ?
>=files     1     0     0     ?       ?        ?        ?
>,files     0     3     2     ?       ?        ?        ?
>
>The OSX, cygwin, mingw and w32_native should be considered (especially
>cygwin and mingw) as "what problems separate from any shell-specific
>issues are there" (hope that makes sense).
>
>Whoever can fill in the blanks and fix the first guesses, please do so.

There is one other category of tools, besides shells, that might cause
problems; build environments. I know that many people consider the
autotools to be seriously broken, but they are in wide use, and many
others argue it's the best we have at the moment.

I ran into problems building in a subdirectory named ,build since it
seems the automake generated Makefile uses a comma (,) as a delimeter in
some of its sed invocations. (/ and | are also used, why the lack of
consistency?)

/M

-- 
Magnus Therning                    (OpenPGP: 0xAB4DFBA4)
address@hidden
http://magnus.therning.org/

The number of the beast - vi vi vi
     -- Delexa Jones

signature.asc
Description: Digital signature