Bug 131667 - Own mozilla plugin dir(s)
Own mozilla plugin dir(s)
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
: EasyFix, Patch
Depends On:
Blocks: FC3Target
  Show dependency treegraph
 
Reported: 2004-09-02 18:50 EDT by Ville Skyttä
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-05 17:33:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Own Mozilla plugin dir(s) (478 bytes, patch)
2004-09-02 18:51 EDT, Ville Skyttä
no flags Details | Diff

  None (edit)
Description Ville Skyttä 2004-09-02 18:50:31 EDT
It would be nice to have kdebase (~ konqueror) to own the mozilla
plugin dirs.

In short: %{_libdir}/mozilla/plugins is the generic location for
mozilla plugins; and plugin packages could have a rpm dependency on
that dir, not a specific browser.  I don't want to have mozilla
installed to be able to use plugins with konqueror...

For more discussion, see bug 131247.  Will attach a suggested patch.
Comment 1 Ville Skyttä 2004-09-02 18:51:52 EDT
Created attachment 103411 [details]
Own Mozilla plugin dir(s)
Comment 2 Ngo Than 2004-09-03 08:21:44 EDT
Ville, it's perhaps better if the plugin package should own the
%{_libdir}/mozilla, %{_libdir}/mozilla/plugins.
Comment 3 Ville Skyttä 2004-09-03 13:30:56 EDT
But that does not help with the initial requirement, it actually would
make it impossible to implement, see bug 131247.

When installing a plugin package, we need a way to specify a
dependency: "this package requires a web browser that loads Mozilla
compatible plugins from $dir".

So a foo-plugin package would have:

   Requires: %{_libdir}/mozilla/plugins

Now, if any _plugin_ package owns that dir, the dependency is not
reliable any more, because it would be satisfied by that plugin, not a
browser.
Comment 4 Ngo Than 2004-09-05 17:33:55 EDT
it's fixed in 3.3.0-2.

Note You need to log in before you can comment on or make changes to this bug.