Roland Mainz wrote:
>
>
> <rant>Why is this /usr/lib/shell/ directory _that_ difficult_ to get via
> ARC ? Somehow I'm starting to regret to have exposed too much detail and
> now we're _bickering_ (sorry for that word but I don't know any better
> word for it) the details down to a sub-atomic level to hell.</rant>
>
If I can offer what I think might be an explanation (I think I said much
the same during yesterday's IRC session):
You've claimed to offer generic functionality to be shared by several
different shells, using a very generic name, and then offered no detail
as to what you intend or what the directory contents will be. It seems
clear that you intend usage which *not* be project private in the least.
Its like asking for a permit to build a new house without specifying
anything other than what neighborhood it will be in. A lot more detail
about what you intend, why this is useful, and how it will be shared
would be useful. I also think that's the kind of detail that justifies
a separate case, rather than trying to piggyback this as a small
addition on another case.
Alternatively, for a truly project private directory, that would
probably not require ARC approval, using a directory like /usr/lib/ksh
or /usr/lib/ksh93 would work. (You'll still need approval in the form
of contracts or somesuch when other projects start to make use of this,
though.)
-- Garrett
