On 11/28/2015 08:02 AM, anlarye wrote:
according to kvirc's website, as of version 2.0 KDE is completely optional.
Generally, information that developers provide about what is optional apply to the application source code, and not to a compiled binary. Optional features can be selected when running the "configure" script (or its equivalent). Once an application has been compiled, many of those options have been fixed. The run-time linker must find the libraries which provide symbols in the application binary, or the application cannot start.
rpm dependencies are *mostly* automatically generated, as Michael pointed out. Those aren't just suggestions that the packager though you should have. The application won't run without them.
If you want to control your dependencies, you could build the application from source, but at that point you have to install gcc and all of the -devel packages for all of the required libraries, which you'll have to determine and install manually. It's a lot more work, and probably doesn't save any space. Or you could modify the spec and tell it not to build against KDE, and build that under mock. Less work, but even more space.
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
