[Bug 457035] Review Request: libproxy - A library handling all the details of proxy configuration

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=457035





--- Comment #11 from Nathaniel McCallum <bugs at natemccallum.com>  2008-10-20 09:06:33 EDT ---
Basically, the idea is this:
1. set the build deps so that all plugins are built
2. tell rpmbuild to ignore the dependencies in the plugins
3. include the plugins in the main package (but don't add their deps to the
rpm)

Again, this is not the standard method, I know.  I'm trying to avoid the
following scenario:

1. John installs an app which depends on libproxy
2. Afterwards, John installs firefox.
3. If the mozjs plugin is included in the base libproxy package, WPAD/PAC will
*just work*.  However, if mozjs is not in the base libproxy package, John will
*also* have to install libproxy-plugin-mozjs to get WPAD/PAC support.

libproxy should always just work, no matter what is installed on the system.

Again, as a packager, I know this flies in the face of conventional packaging
wisdom.  However, the user has a lot to gain by doing it this way.

If rpmbuild cannot be told to ignore DSO shlib deps, then I don't see any other
solution than one-package-per-plugin.

Great to hear about neon!

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.