Lars Marowsky-Bree wrote:
On 2006-06-12T09:09:02, Alan Robertson <[EMAIL PROTECTED]> wrote:
This will ONLY happen if it has been incorrectly specified. So, I don't
see a reason to patch it out for anyone. It will only happen if someone
specifically specified --libdir=/usr/lib64 AND /usr/lib64 doesn't exist.
If the commandline arguments were detected to be _wrong_, we probably
should bail out with an error - because we can't give the user what
they've asked for.
In general, I agree with you. I'm about as anal as they come -
typically. But, in this particular case, I'd like to just correct it.
It's a different (and kind of half-ass) way of solving the same problem
you didn't like my previous solution to.
Whatever else it is, it _should_ be pretty harmless. [famous last words].
And, I'm trying to minimize the risk of these changes to our build
process - since we are trying to get 2.0.6 out ;-). In my opinion, this
change is low risk.
The other half of it is to put the --libdir= setting back into
ConfigureMe. I think this is a reasonable compromise for something we
have to solve quickly and at low risk.
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
