# from Ken Williams
# on Friday 23 January 2009 15:26:
>> Right. I think the unix users have also gotten used to
>> administration of things which use PREFIX. So, for situations where
>> an admin would expect an application to install stuff in
>> $PREFIX/share/application -- what is our solution?
>
>Our solution in that case is just to use $PREFIX (a.k.a. --prefix).
No, no. Different question.
>If it's what the user needs there's nothing wrong with using it. The
>problem with it was that in many cases it just didn't solve the user's
>needs, so something different was needed.
>...
> There's no way the module author can anticipate where on the user's
> system stuff should be put.
This is the question. If an *author* wants to put something in
$PREFIX/share/myapp, what do they need to do such that "$PREFIX/share"
is e.g. /usr/local/share (where (and only where) that makes sense)?
And in all of the other cases, what stands-in for "$PREFIX/share" from
the author's point of view such that M::B can perhaps DTRT and this
does not become an author education project?
Adam has proposed (I think) that Config.pm can specify a sharedir and (I
think) that we can fallback to an 'auto/' location in @INC as per
File::ShareDir. I posit that this then becomes a vendor+user education
project, but haven't examined it in much detail.
--Eric
--
"Everything goes wrong all at once."
--Quantized Revision of Murphy's Law
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
