taskGnash - The GNU Flash player - Tasks: task #7340, Wrong information about firefox...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #7340: Wrong information about firefox plugin in the manual

Submitter:  Benjamin Wolsey <bwy>
Submitted:  Sat 29 Sep 2007 12:58:01 PM UTC
   
 
Should Start On:  - Should be Finished on:  -
Category:  None Priority:  5 - Normal
Status:  None Privacy:  Public
Assigned to:  None Percent Complete:  0%
Open/Closed:  Open Effort:  0.00

Jump to the original submission

Sat 29 Sep 2007 12:58:01 PM UTC, comment #6: 

This item has been reassigned from the project Gnash - The GNU Flash player bugs tracker to your tracker.

The original report is still available at bugs #21184

Following are the information included in the original report:

[field #0]                  Item ID: 21184
[field #1]                 Group ID: 8191
[field #2]              Open/Closed: Open
[field #3]                 Severity: 3 - Normal
[field #4]                  Privacy: Public
[field #9]                 Category: plugin
[field #10]             Submitted by: bwy
[field #11]              Assigned to: bwy
[field #12]             Submitted on: Freitag 28.09.2007 um 20:06
[field #13]                  Summary: Wrong information about firefox plugin in the manual
[field #14]      Original Submission: Someone on IRC, who had RTFM, couldn't find out how to set the firefox plugin directory to ~/.mozilla/plugins rather than ~/.firefox/plugins, which is what the manual says.

docs/C/usermanual/installation/install.xml

As I understand it, we build the plugin from our own headers (so all the stuff about headers is wrong) and the plugin is always installed in ~/.mozilla/plugins unless otherwise specified.

I'll fix at least first part when I have time to check more carefully, or once someone has confirmed that's correct.
[field #16]               Item Group: None
[field #17]                   Status: None
[field #18]        Component Version: None
[field #19]         Operating System: None
[field #20]          Reproducibility: None
[field #21]               Size (loc): None
[field #22]            Fixed Release: None
[field #23]          Planned Release: None
[field #24]                   Effort: 0.00
[field #28]                 Priority: 5 - Normal
[field #31]         Percent Complete: 0%
[field #33]                  Release: None
[field #58]     Custom Select Box #1: None
[field #59]     Custom Select Box #2: None
[field #60]     Custom Select Box #3: None
[field #61]     Custom Select Box #4: None
[field #62]     Custom Select Box #5: None
[field #63]     Custom Select Box #6: None
[field #64]     Custom Select Box #7: None
[field #65]     Custom Select Box #8: None
[field #66]     Custom Select Box #9: None
[field #67]    Custom Select Box #10: None

 Benjamin Wolsey <bwy>
Group Member
Sat 29 Sep 2007 12:58:00 PM UTC, comment #5: 

Transferring discussion to a task for later.

 Benjamin Wolsey <bwy>
Group Member
Sat 29 Sep 2007 07:42:14 AM UTC, comment #4: 

I think that at present, while most people who build are testing gnash and just want the plugin installed where they can automatically use it, it's fine as it is. Requiring more installation steps or manual copying of files just means more people on IRC asking how to get youtube working.

Packagers ought to be able to read instructions and set the plugin directory themselves.

This might be better left for later, once lots of people want to install gnash system wide.

 Benjamin Wolsey <bwy>
Group Member
Sat 29 Sep 2007 07:27:01 AM UTC, comment #3: 

The problem with installing in ~/.mozilla/plugins is that it's a user directory, while make install is typically done as root. People that don't use sudo for various reasons run make install with su -c, which makes the process run by the root user. Configure, run as the user, sets it to be the right user directory, but the created files and directories are owned by root and unwriteable by the user.

Plus, source-based package managers usually configure, make, and install packages as root, so it'd be put into root's home directory where users can't even look. Installing packages from package managers shouldn't go about putting plugins into user directories because the package managers operate system wide.

IMHO, make install should put the plugin into the correct directory as prefixed with --prefix or whatever (global by default), and if a user wants to install the plugin on a single user, they'd copy it from the gnash directory where it was built to the browser's user plugin directory. So perhaps a configure option to disable installing a plugin while still building it, and there could be user-run install scripts to copy the built lib to the correct user directory automatically. So something like:

./configure --disable-plugin-install (configures and sets to not install the plugin)
make (build the libs and plugin)
su -c "make install" (install the libs)
./install-mozilla-plugin [user name] (install the built plugin to the given user's local plugin dir)

 Chris Robinson <kcat>
Sat 29 Sep 2007 05:56:00 AM UTC, comment #2: 

See also bug #20887.

I'd think the default sfor nsapi hould be system-install and the configure switch (which could be renamed to include the 'nsapi' string) should be used to override. We also need a configure switch to change install dir for the kparts one I guess.

 Sandro Santilli <strk>
Group Member
Fri 28 Sep 2007 08:10:25 PM UTC, comment #1: 

Currently it does get installed in ~/.mozilla/plugins, as all browsers look there. We also did copy the mozilla SDK for NSAPI to the plugin directory so people don't have to install that package. The reason we install in the users home directory is otherwise, they'd have to be root, and the changes would be global.

 Rob Savoye <rsavoye>
Group administrator
Sat 29 Sep 2007 12:58:01 PM UTC, original submission:  

Someone on IRC, who had RTFM, couldn't find out how to set the firefox plugin directory to ~/.mozilla/plugins rather than ~/.firefox/plugins, which is what the manual says.

docs/C/usermanual/installation/install.xml

As I understand it, we build the plugin from our own headers (so all the stuff about headers is wrong) and the plugin is always installed in ~/.mozilla/plugins unless otherwise specified.

I'll fix at least first part when I have time to check more carefully, or once someone has confirmed that's correct.

 Benjamin Wolsey <bwy>
Group Member

 

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

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by kcat (Posted a comment)
  • -email is unavailable- added by strk (Posted a comment)
  • -email is unavailable- added by rsavoye (Posted a comment)
  • -email is unavailable- added by bwy (Submitted the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-09-29 bwy Reassign itemGnash - The GNU Flash player, bug #21184 Gnash - The GNU Flash player, task #7340

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.14-8eb0.
    Corresponding source code