Page 1 of 1

firefox module

Posted: 23 Mar 2016, 17:32
by port
Is it any reason to install firefox system wide rather than opt-installed in official base module?

I think it will be simple to just take firefox install tgz which works right autocontained (locally or in /opt/firefox) and just make a 04-firefox module to install it in /opt/firefox making updates easier

it would be something like:

Code: Select all

% mkdir -p tmp/opt
% curl https://download-installer.cdn.mozilla.net/pub/firefox/releases/45.0.1/linux-x86_64/en-GB/firefox-45.0.1.tar.bz2 > firefox-45.0.1.tar.bz2  
% cd tmp/opt 
% tar xvjf ../../firefox-45.0.1.tar.bz2
% cd ../..
% dir2xzm tmp 04-firefox.xzm 
% cp 04-firefox.xzm firefox-45.0.1-x86_64-en_GB.xzm  # for users exchange

Re: firefox module

Posted: 25 Mar 2016, 06:53
by Rava
port wrote:

Code: Select all

% mkdir -p tmp/opt
% cd tmp/opt 
% curl https://download-installer.cdn.mozilla.net/pub/firefox/releases/45.0.1/linux-x86_64/en-GB/firefox-45.0.1.tar.bz2 > firefox-45.0.1.tar.bz2  
% tar xvjf firefox-45.0.1.tar.bz2
% cd ..
% dir2xzm tmp 04-firefox.xzm 
% cp 04-firefox.xzm firefox-45.0.1-x86_64-en_GB.xzm  # for users exchange
That would put the downloaded firefox-45.0.1.tar.bz2 into the new xzm as well, next to the opt folder, or do I misread your code?

Re: firefox module

Posted: 25 Mar 2016, 16:17
by Ed_P
You can also put newer versions of firefox as modules in the modules folder and leave the 04 module there. That way the Porteus firefox settings for search and homepage and etc stay the same.

Re: firefox module

Posted: 29 Mar 2016, 16:00
by port
Rava wrote: That would put the downloaded firefox-45.0.1.tar.bz2 into the new xzm as well, next to the opt folder, or do I misread your code?
you're right, already edited, thanks

Re: firefox module

Posted: 29 Mar 2016, 16:15
by port
Ed_P wrote:You can also put newer versions of firefox as modules in the modules folder and leave the 04 module there. That way the Porteus firefox settings for search and homepage and etc stay the same.
yes, but my question is why is 04-firefox module built that way when not necessary. Doing that you introduce an unwanted dependency with usernames. Wouldn't be better to just avoid creating a home/guest folder and root folder only used to keep .mozilla configuration and Downloads directory and just let firefox create them properly when first run? After all you will have /home and /root under changes coverage or at least they would be created in memory after booting, so why to force their creation in the module?

So my proposal is to simply remove /home/guest and /root from module 04-firefox (or 04-whatever)

A second step would be to avoid system wide installation, replacing /usr with /opt ( /var will stay)

Re: firefox module

Posted: 30 Mar 2016, 01:18
by brokenman
After all you will have /home and /root under changes coverage ... so why to force their creation in the module?
There are certain settings we want to give as default such as the duckduckgo search engine by default which helps Porteus with revenue. Please use it and help Porteus.

Re: firefox module

Posted: 12 Apr 2016, 05:13
by brokenman
Mainly duckduckgo but in the next version I will also disable automatic update since a guest user doesn't have correct permissions to update. There will be a script included in the next version for people to auto update chrome and firefox.

PS: The avatar is mildly distracting, but very cool. I have no problem with it.

Re: firefox module

Posted: 14 Apr 2016, 00:12
by Rava
brokenman wrote:There will be a script included in the next version for people to auto update chrome and firefox.
Maybe also one for Palemoon as well?
And does the update script include the flash player?

Re: firefox module

Posted: 14 Apr 2016, 01:27
by brokenman
The script includes updating fçashplayer. Palemoon is not included at this time. Only firefox, chrome and opera. I may include another since chrome has dropped support for 32bit already.

Re: firefox module

Posted: 14 Apr 2016, 02:57
by Rava
brokenman wrote:The script includes updating fçashplayer. Palemoon is not included at this time. Only firefox, chrome and opera. I may include another since chrome has dropped support for 32bit already.
If you PM me the script early enough, maybe I can tweak it to include PM?

BTW, when is Porteus 3.2 rc1 starting to come? Is there a time map already somewhere?

Re: firefox module

Posted: 15 Apr 2016, 01:54
by brokenman
If you PM me the script early enough, maybe I can tweak it to include PM?
You can find the live scripts here. They are designed to work on Porteus v3.2rc1 and above.

BTW, when is Porteus 3.2 rc1 starting to come? Is there a time map already somewhere?
I am uploading the last of it tonight. The link will be made available then.

Porteus will include an update function so that when openssl is updated you can pull the update.

Re: firefox module

Posted: 16 Apr 2016, 06:07
by Rava
Evan wrote:Porteus will include an update function so that when openssl is updated you can pull the update.

Awesome as they keep having updates since the heartbleed fisaco. :)
You mean, my update module of openssl+openssl-solibs-1.0.1s-x86_64-1 is no longer the newest version? :(

Re: firefox module

Posted: 16 Apr 2016, 08:01
by Rava
When I created my module, there was only the 1.0.1 branch available, no 1.0.2 version for slackware... so I skipped it...
Did you find a current 1.0.2 openssl+openssl-solibs- for Slackware x86-64 ?

Re: firefox module

Posted: 16 Apr 2016, 08:42
by Rava
Evan wrote:I know everyone on here wants Slackware but in my opinion i think Brokenman's Arch version as a rolling release is the best way forward as Linux is regularly being exploited via the web now and needs to be kept updated.
You can keep a non rolling release like Slackware up to date as well, but like you said, you would need to concentrate on checking for updates for certain core components, like, well, openssl+openssl-solibs.


Anyhow, why do we discuss this in a thread about "firefox module"?

Re: firefox module

Posted: 16 Apr 2016, 09:15
by Rava
^
Now it makes sense, *facepalm*