On Saturday 25 October 2003 21:23, John Anderson wrote:
I didn't make myself clear :
> If a package ends up in /usr/local, either the person
> doing the install compiled from source using an ordinary ./configure, or
> they changed the default install path.
I did the former : compiled jack from source, ./configure ; make ; make
install.
> So my thinking is that somebody
> knowledgeable enough to do one of those things would also be
> knowledgeable enough to make sure that PKG_CONFIG_PATH is set correctly
> when they get an error message trying to compile another package.
And as I said, I didn't know anything about pkg-config two days ago. I had no
idea that this variable was even existing. I dug it up from the pkg-config
manpage right after trying to test your patch.
> Maybe that's too much of an assumption?
Apparently yes :-).
I don't see what's the problem here, we're just adding a path to that
variable. Either the user already did it and the change won't make a
difference, or he didn't and we save him the same kind of search I did. I'm
pretty sure both Chris and Rich would have had the same problem as me, since
none of us is very keen on this kind of issues.
--
Guillaume.
http://www.telegraph-road.org
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
