Mario Klebsch wrote:
Why? gEDA would always use the one that it includes in it's package because it is known to work.
So if gEDA needs Foo then why not compile it into the geda apps.
I would vote against this, because this is even more magic. configure would have to determine, wether to use the packaged lib or the system one. It must perform all the decisions, that installing package foo might involve.
We are already seeing this with our cad tool vendors. They will include a copy perl with their apps and they will
use that rather than the one on the system because it reduces the number of support calls.
John Eaton
that may have some security implications.
Developers here have enough to do without having to track vulnerabilities in lots of packages only there because the host system might not have them, orr the wrong version.
EDA company X can probaby assume that the workstations with their installs are not exposed directly to the web. Thats less true for
boxes running geda code I suspect.
And the way some EDA vendors install java libraries and web browsers is not really a model I'd like to see copied..
I'd still suggest some folk help to package these tools into debian , fedora and whatever SUSE uses package repositories.
john
