bugGnash - The GNU Flash player - Bugs: bug #16582, weird install location for...

 
 

bug #16582: weird install location for libgnashplugin.so

Submitted by:  Rui Miguel Seabra <cyclops>
Submitted on:  Sun 14 May 2006 05:15:21 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Release: NoneStatus: Invalid
Privacy: PublicAssigned to: Rob Savoye <rsavoye>
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sun 14 May 2006 05:32:52 PM UTC, comment #5:

The plugin must be installed where Firefox or Mozilla expects to find it. This restricts the location to the browser specific directories for plugins. Installing the plugin in any variation of PREFIX is just plain wrong. The plugin isn't a normal shared library, it's only used by the browser.

At one time Gnash installed the plugin into the system directory for browser plugins. This required one to be root to do an install, so putting it in the users home directory, the only one with the proper permissions for people building from source, is the correct thing to do as determined by the Gnash development community.

With no options, Gnash installs the plugin in the correct place. With --plugindir, it goes in your specified directory.

Rob Savoye <rsavoye>
Project AdministratorIn charge of this item.
Sun 14 May 2006 05:26:40 PM UTC, comment #4:

ok, I don't mind needlessly typing a few more options but the default when plugindir is not used should be something smarter than an user's HOME!

like somewhere under PREFIX/lib or PREFIX/share or libexec or whatever.

Rui Miguel Seabra <cyclops>
Sun 14 May 2006 05:24:27 PM UTC, comment #3:

--prefix doesn't effect the plugin. Use --plugindir instead. The plugin has to be installed where the browser expects to find it's plugin files, not where all the application libraries go. The plugin still looks in $prefix to find shared libraries regardless of where it's installed.

Rob Savoye <rsavoye>
Project AdministratorIn charge of this item.
Sun 14 May 2006 05:21:31 PM UTC, comment #2:

I should have been more clear, but since I seperated my experience in 3 but items some info got lost for this one.

I used --prefix and DESTDIR so how could it do that?

Rui Miguel Seabra <cyclops>
Sun 14 May 2006 05:19:52 PM UTC, comment #1:

Without any directory specified with --plugindir=DIR, the plugin has to get installed somplace. The users home directory is the traditional location for this in either the .mozilla or .firefox plugins, where they get laoded just fine by the browser. You can also set DESTDIR at "make install" time to have the plugin go elsewhere. This is usually only used when building packages though.

Rob Savoye <rsavoye>
Project AdministratorIn charge of this item.
Sun 14 May 2006 05:15:21 PM UTC, original submission:

~/.firefox/plugins/ is not where it should go, how did it get to install there? weird...

Rui Miguel Seabra <cyclops>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 3 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Sun 14 May 2006 05:19:52 PM UTCrsavoyeStatusNone=>Invalid
  Assigned toNone=>rsavoye
  Open/ClosedOpen=>Closed

Back to the top


Powered by Savane 3.1-cleanup1