guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1.6.0 problems with libguilereadline-v-12 and fix


From: Thien-Thi Nguyen
Subject: Re: 1.6.0 problems with libguilereadline-v-12 and fix
Date: Tue, 24 Sep 2002 23:09:56 -0700

   From: address@hidden (Paul Jarc)
   Date: Sat, 21 Sep 2002 17:51:04 -0400

   I agree that guile-config should be honest *by default*, but if I
   explicitly express that I want to refer to Guile's files via a
   different path than the one guile-config already knows about, why make
   it any harder for me than it has to be?

at the moment, i don't believe anyone is actively trying to make things
difficult for you.  i'm glad you bring up "difficulty", however.  to
take your proposal seriously i request a failure analysis: how can the
proposed mechanism be abused (perhaps unintentionally)?  what are the
remedies in those cases?  how can nested build/install/dist scenarios
fail?  how can this interact badly w/ auto* practice?  these questions
are examples to get you started; ping me if you want more.

introducing env var sensitivity is not a light step to take; many (good)
programmers will find fault w/ such action-at-a-distance behavior if we
don't do it right.  are we afraid of their criticism?  no.  do we want
to waste time later countering it?  no.  so let us flay the concept now
as if we were clueless naysayers attempting to heap FUD on a working
design.

   It's much easier for guile-config to output a different path than it
   is for me to fix it afterwards; I would have to delve into the
   internals of each package that uses guile-config.

along w/ the full (ab|mis)usage analysis (preferably texinfo but plain
text is fine, too), feel free to submit a small patch to guile-config.

thi




reply via email to

[Prev in Thread] Current Thread [Next in Thread]