SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by jong357 Nice.... I never keep up with the changelog. I'm sure Pats script is very different from mine. I'll have to look at it.
yeah, pat decided to use the official binaries, so the slackware firefox build script doesn't do any compiling...
Quote:
# This is not a source build script. Rather, it builds a Slackware
# package from the official binary tarball available from mozilla.org.
# Using the official binaries seems like the most direct way to satify
# the Mozilla project's concerns about quality control (and thus to
# provide the most quality-certified package possible), and therefore
# be able to use the official trademarks and logos.
#
# Thanks to the folks at the Mozilla Foundation for permission to
# distribute this, and for all the great work! :-)
Yea, I just saw that. Funny... I think I'll use my own script actually. I've been doing his 'build script' for over a year and decided it was kind of lame. Oh well.....
even more interesting is that it is a i686 package. perhaps pat is thinking of increasing the arch of all X packages to i686 as I doubt anyone is still using X with something less than a pentium 2. anyway, it wont give any big perfomance effect in the end but it will make the packages a bit smaller at least.
Yea, the 'official' binaries were compiled with i686/xft/gtk so thats what the slak-pak is going to be. Makes me kind of wonder if Pat is truely concerned with "to satify the Mozilla project's concerns about quality control (and thus to provide the most quality-certified package possible)" or if he just didn't want 2 more "big" packages to maintain..... Not a big deal to me. I'll just keep using my script. Works quite nicely. I just have this ideal about having all packages i486 even tho I'm running a Pentium4 3.0ghz HT system....
I always downloaded the pre-compiled package straight from firefox/thunderbird. Unpacked it and then rearanged things to make it into a "slak-pak".... That's all he is doing. Same thing I've been doing since version .6 or .7
Originally posted by jong357 Nice.... I never keep up with the changelog. I'm sure Pats script is very different from mine.
Well, he packs the official binaries version. He does not compile it from source The only thing he touches is to add a javascript line to use Thunderbird as default for mailto operation.
SO firefox package can be used by slack10.1 slack10 and maybe users with even older slackware since the official mozilla binaries are compiled with an older glib library.
I tried it in 10.1 and it works great.
Quote:
Originally posted by rovitotv If you look at the date of my question you will realize this was posted _BEFORE_ the change log was updated to include Firefox. Maybe I can read Pat's mind?
TVR
The first thing I did when I upgrated to slack10.1 was to remove netscape and mozilla and install firefox. Maybe I can also read his mind.
Originally posted by jong357 I always downloaded the pre-compiled package straight from firefox/thunderbird. Unpacked it and then rearanged things to make it into a "slak-pak".... That's all he is doing. Same thing I've been doing since version .6 or .7
oh, okay... i see what you mean... yeah, that's what i've been doing also (making my own slackpack from the official binaries)...
i think it's nice to build your own firefox, though... ;-)
just curious, are there any noticable differences between a firefox 1.0.1 compiled with your script and the official 1.0.1 binaries?? like, did you add or subtract anything maybe?? just wondering...
Originally posted by chbin even more interesting is that it is a i686 package. perhaps pat is thinking of increasing the arch of all X packages to i686 as I doubt anyone is still using X with something less than a pentium 2. anyway, it wont give any big perfomance effect in the end but it will make the packages a bit smaller at least.
If he was going to use the official binaries he did not have any other option.
I realize that the i686 package is not built from source in slack, but more the likely kernel 2.6 will be going into slack current to test for the slack 11 release. Hence, pat will have to recompile glibc with the new headers and any package that wants to take advantage of the new interfaces. Hence, i big recompile is coming sooner or later. so since that is a big project might as well bump everything up.
Originally posted by chbin I realize that the i686 package is not built from source in slack, but more the likely kernel 2.6 will be going into slack current to test for the slack 11 release. Hence, pat will have to recompile glibc with the new headers and any package that wants to take advantage of the new interfaces. Hence, i big recompile is coming sooner or later. so since that is a big project might as well bump everything up.
There will be major changes in slackware 11, like dropping 2.4 kernel support, and as you said a big recompile is coming, but i have the filling that the arch will stay i486 and firefox won't be compiled from source.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.