Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use system dependencies #112

Open
guijan opened this issue Jun 25, 2024 · 1 comment
Open

Use system dependencies #112

guijan opened this issue Jun 25, 2024 · 1 comment

Comments

@guijan
Copy link
Contributor

guijan commented Jun 25, 2024

No system wants to package a program that has dependencies baked into the source tree. It's a nightmare to deal with for package maintainers, they don't want to contribute fixes upstream and still experience bugs that were already fixed because they didn't make it to copies of the code, or to find and patch all copies of the same code that all suffer from the latest security vulnerability, among other issues.

It's bad for users too because programs that compile on many platforms are few and it's common for the packaged version of a library to need patches to get it to build. If this program can't use the system versions of its libraries, anyone compiling it has to go figure out how to get those fixes in the local copy of the source code.

Please provide an option to use system versions of dependencies. I suggest also making it the default without an automatic fallback, as users should try installing the dependencies before using the local copy. This should also reduce overall memory usage and compile times.

@DarthMew
Copy link
Collaborator

I believe @LibretroAdmin can provide a much better answer than I can regarding why it is the way it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants