Slackware drops GNOME, restores Mozilla
From: | mrgoblin-AT-dunedin.lug.net.nz | |
To: | changelog-AT-mrgoblin.is-a-geek.org | |
Subject: | Slackware Changelog Notice!! | |
Date: | Mon, 28 Mar 2005 10:41:37 +1200 |
Slackware Current ChangeLog Notice. The following additions have been made to The Current ChangeLog.txt Please do not Reply to this email ------------------------------------------------------------------- New Entry: Sat Mar 26 23:04:41 PST 2005 New Entry: a/hotplug-2004_09_23-noarch-2.tgz: Blacklisted a few more modules: New Entry: snd-atiixp-modem, snd-intel8x0m, snd-via82xx-modem, and intelfb. New Entry: Thanks to Tomas Matejicek, Piter PUNK, and Tobias Svensson for reporting New Entry: the problems with hotplug auto-loading these (in the rare event that your New Entry: machine actually needs them, they can be manually loaded somewhere else New Entry: in the boot scripts, such as rc.modules.) New Entry: a/infozip-5.52-i486-1.tgz: Upgraded to unzip-5.52 and zip-2.31. New Entry: a/gettext-0.14.3-i486-1.tgz: Upgraded to gettext-0.14.3. New Entry: ap/mysql-4.0.24-i486-1.tgz: Upgraded to mysql-4.0.24. New Entry: d/automake-1.9.5-noarch-1.tgz: Upgraded to automake-1.9.5. New Entry: d/gettext-tools-0.14.3-i486-1.tgz: Upgraded to gettext-0.14.3. New Entry: d/libtool-1.5.14-i486-1.tgz: Upgraded to libtool-1.5.14. New Entry: gnome/*: Removed from -current, and turned over to community support and New Entry: distribution. I'm not going to rehash all the reasons behind this, but it's New Entry: been under consideration for more than four years. There are already good New Entry: projects in place to provide Slackware GNOME for those who want it, and New Entry: these are more complete than what Slackware has shipped in the past. So, if New Entry: you're looking for GNOME for Slackware -current, I would recommend looking at New Entry: these two projects for well-built packages that follow a policy of minimal New Entry: interference with the base Slackware system: New Entry: New Entry: http://gsb.sf.net New Entry: http://gware.sf.net New Entry: New Entry: There is also Dropline, of course, which is quite popular. However, due to New Entry: their policy of adding PAM and replacing large system packages (like the New Entry: entire X11 system) with their own versions, I can't give quite the same sort New Entry: of nod to Dropline. Nevertheless, it remains another choice, and it's _your_ New Entry: system, so I will also mention their project: New Entry: New Entry: http://www.dropline.net/gnome/ New Entry: New Entry: Please do not incorrectly interpret any of this as a slight against GNOME New Entry: itself, which (although it does usually need to be fixed and polished beyond New Entry: the way it ships from upstream more so than, say, KDE or XFce) is a decent New Entry: desktop choice. So are a lot of others, but Slackware does not need to ship New Entry: every choice. GNOME is and always has been a moving target (even the New Entry: "stable" releases usually aren't quite ready yet) that really does demand a New Entry: team to keep up on all the changes (many of which are not always well New Entry: documented). I fully expect that this move will improve the quality of both New Entry: Slackware itself, and the quality (and quantity) of the GNOME options New Entry: available for it. New Entry: New Entry: Folks, this is how open source is supposed to work. Enjoy. :-) New Entry: New Entry: kde/kdeaccessibility-3.4.0-i486-1.tgz: Upgraded to kdeaccessibility-3.4.0. New Entry: kde/kdeaddons-3.4.0-i486-1.tgz: Upgraded to kdeaddons-3.4.0. New Entry: kde/kdeadmin-3.4.0-i486-1.tgz: Upgraded to kdeadmin-3.4.0. New Entry: kde/kdeartwork-3.4.0-i486-1.tgz: Upgraded to kdeartwork-3.4.0. New Entry: kde/kdebase-3.4.0-i486-1.tgz: Upgraded to kdebase-3.4.0. New Entry: kde/kdebindings-3.4.0-i486-1.tgz: Upgraded to kdebindings-3.4.0. New Entry: kde/kdeedu-3.4.0-i486-1.tgz: Upgraded to kdeedu-3.4.0. New Entry: kde/kdegames-3.4.0-i486-1.tgz: Upgraded to kdegames-3.4.0. New Entry: kde/kdegraphics-3.4.0-i486-1.tgz: Upgraded to kdegraphics-3.4.0. New Entry: kde/kdelibs-3.4.0-i486-1.tgz: Upgraded to kdelibs-3.4.0. New Entry: kde/kdemultimedia-3.4.0-i486-1.tgz: Upgraded to kdemultimedia-3.4.0. New Entry: kde/kdenetwork-3.4.0-i486-1.tgz: Upgraded to kdenetwork-3.4.0. New Entry: kde/kdepim-3.4.0-i486-1.tgz: Upgraded to kdepim-3.4.0. New Entry: kde/kdesdk-3.4.0-i486-1.tgz: Upgraded to kdesdk-3.4.0. New Entry: kde/kdetoys-3.4.0-i486-1.tgz: Upgraded to kdetoys-3.4.0. New Entry: kde/kdeutils-3.4.0-i486-1.tgz: Upgraded to kdeutils-3.4.0. New Entry: kde/kdevelop-3.2.0-i486-1.tgz: Upgraded to kdevelop-3.2.0. New Entry: kde/kdewebdev-3.4.0-i486-1.tgz: Upgraded to kdewebdev-3.4.0. New Entry: kde/koffice-1.3.5-i486-3.tgz: Recompiled. New Entry: kde/qt-3.3.4-i486-1.tgz: Upgraded to qt-3.3.4 (with -stl). New Entry: l/atk-1.9.1-i486-1.tgz: Upgraded to atk-1.9.1. New Entry: l/arts-1.4.0-i486-1.tgz: Upgraded to arts-1.4.0. New Entry: l/expat-1.95.8-i486-1.tgz: Upgraded to expat-1.95.8. New Entry: (thanks to Alak Trakru for updating the DESTDIR patch) New Entry: l/gtk+2-2.6.4-i486-1.tgz: Upgraded to gtk+-2.6.4. New Entry: l/libart_lgpl-2.3.17-i486-1.tgz: Upgraded to libart_lgpl-2.3.17. New Entry: l/libglade-2.4.2-i486-1.tgz: Upgraded to libglade-2.4.2. New Entry: l/libgsf-1.11.1-i486-1.tgz: Upgraded to libgsf-1.11.1. New Entry: l/libidl-0.8.5-i486-1.tgz: Upgraded to libidl-0.8.5, moved from /gnome. New Entry: (this is used by Mozilla) New Entry: l/libmikmod-3.1.11a-i486-1.tgz: Upgraded to libmikmod-3.1.11a, moved from New Entry: /gnome. (this is used by XMMS) New Entry: l/libxml2-2.6.18-i486-1.tgz: Upgraded to libxml2-2.6.18. New Entry: l/libxslt-1.1.13-i486-1.tgz: Upgraded to libxslt-1.1.13. New Entry: l/orbit-0.5.17-i386-1.tgz: Removed obsolete ORBit. New Entry: l/pango-1.8.1-i486-1.tgz: Upgraded to pango-1.8.1. New Entry: l/shared-mime-info-0.16-i486-1.tgz: Upgraded to shared-mime-info-0.16, moved New Entry: from /gnome. New Entry: l/startup-notification-0.8-i486-1.tgz: Upgraded to startup-notification-0.8. New Entry: n/nail-11.22-i486-1.tgz: Upgraded to nail-11.22. New Entry: n/samba-3.0.13-i486-1.tgz: Upgraded to samba-3.0.13. New Entry: xap/gaim-1.2.0-i486-1.tgz: Upgraded to gaim-1.2.0 and gaim-encryption-2.36. New Entry: (compiled against mozilla-1.7.6) New Entry: xap/gimp-2.2.4-i486-1.tgz: Upgraded to gimp-2.2.4. New Entry: xap/jre-symlink-1.0.2-noarch-1.tgz: Upgraded Java link for Firefox 1.0.2. New Entry: xap/mozilla-1.7.6-i486-1.tgz: Replaced Mozilla, upgraded to 1.7.6. New Entry: While I got surprisingly few negative comments about Mozilla's previous New Entry: removal from -current, I have decided put it back. Why? Well, it is a good New Entry: piece of software with a long and respected history. So, why then, would I New Entry: have removed it before? Dose my mind? ;-) My answer at the time was New Entry: that once the Mozilla Foundation indicated that the primary future direction New Entry: would be with Firefox and Thunderbird, and that active development on the New Entry: traditional Mozilla suite would end, then the writing was already on the New Entry: wall. Slackware does not aim to be a Home for Orphaned Software, and if New Entry: upstream ceases to support something, then I'll usually follow that lead in New Entry: fairly short order. However, Mozilla is being restored for now since I know New Entry: it has a strong following, but also because it provides some features (like New Entry: the composer) that FF/TB do not, and because the libraries are used in GAIM New Entry: to provide support for MSN. I am aware that GNUTLS can also be used for this New Entry: purpose, but after looking that (and its dependencies) over, I'd prefer to New Entry: not see that enter Slackware at this time. OpenSSL could also be used for New Entry: this support in GAIM, but unfortunately there is an incompatibility between New Entry: GAIM's GPL license and OpenSSL's BSD-with-advertising-clause license. This New Entry: resulting snafu reminds me of a short article by Grigor Gatchev that I New Entry: recently read on NewsForge, called "Metalicensing". It's still online, and New Entry: I'd suggest it (and the author's site) for a little additional reading on New Entry: the topic of free license incompatibilities, and how we might avoid New Entry: unintentionally setting these kinds of traps for ourselves. I look forward New Entry: to a world with the least possible restrictions on software development, and New Entry: I think that step one is to be on guard against accidentally tying our own New Entry: hands behind our backs. Having a redundant (but differently free) version New Entry: of every component and needing them _all_ to create a complete system does New Entry: not strike me as the optimal solution. New Entry: /* end "pseudo blog" :-) I hope I didn't offend anybody affiliated with New Entry: any of these fine projects, as that is definately not my intent... */ New Entry: Back to the topic of _this package_, this Mozilla release fixes more than a New Entry: dozen security issues (many of which are probably minor and unlikely to New Entry: occur in real life, but you be the judge.) New Entry: Please see mozilla.org for a complete list. New Entry: (* Security fix *) New Entry: xap/mozilla-firefox-1.0.2-i686-1.tgz: Upgraded to firefox-1.0.2. New Entry: Fixes a GIF heap overflow and some other security issues. New Entry: Please see mozilla.org for a complete list. New Entry: (* Security fix *) New Entry: xap/mozilla-thunderbird-1.0.2-i686-1.tgz: Upgraded to thunderbird-1.0.2. New Entry: Fixes a GIF heap overflow and some other security issues. New Entry: Please see mozilla.org for a complete list. New Entry: (* Security fix *) New Entry: xap/xfce-4.2.1.1-i486-1.tgz: Upgraded to xfce-4.2.1.1. New Entry: xap/xscreensaver-4.21-i486-1.tgz: Upgraded to xscreensaver-4.21. New Entry: extra/k3b/k3b-0.11.23-i486-1.tgz: Upgraded to k3b-0.11.23. New Entry: extra/parted/parted-1.6.22-i486-1.tgz: Upgraded to parted-1.6.22. New Entry: testing/packages/gnupg-1.4.1-i486-1.tgz: Upgraded to gnupg-1.4.1. New Entry: +--------------------------+ If for some reason you no longer wish to be notified of Entries to the ChangeLog Please send an email To: mrgoblin@userlocal.com Subject: "unsubscribe slacklog" and the subscribed email address in the body of the message. Thank you mRgOBLIN
Posted Mar 28, 2005 20:42 UTC (Mon)
by cbcbcb (subscriber, #10350)
[Link] (6 responses)
Posted Mar 28, 2005 21:29 UTC (Mon)
by ekg (guest, #27035)
[Link]
Posted Mar 28, 2005 22:24 UTC (Mon)
by allesfresser (guest, #216)
[Link] (1 responses)
Posted Mar 28, 2005 22:43 UTC (Mon)
by allesfresser (guest, #216)
[Link]
Posted Mar 29, 2005 3:25 UTC (Tue)
by nkoozer (guest, #5553)
[Link] (1 responses)
Posted Mar 29, 2005 16:26 UTC (Tue)
by slacker (guest, #28841)
[Link]
if you have 3 or more machines, then just mirror current tree locally inside DMZ, (if you are not bleeding edge man, and stick to version not current, nice way is just to download iso, mount, export, that way its kind a more organised ;)...
of course you will need only disc-1 if you dont use gui
slackin is phun
arno
Posted Apr 1, 2005 19:45 UTC (Fri)
by danieldk (subscriber, #27876)
[Link]
Both rsyncing Slack, or using an update tool, is described in:
Slackware drops GNOME, restores Mozilla
Can a slackware fan tell me what features are provided for upgrading a
slackware installation these days. Is it debian-style (upgrade with the
system online) or redhat-style (take the system down and re-run the
installer in upgrade mode)?
Thanks for any info
Usually you upgrade packages online, and then reboot to use the new kernel if that has changed. If you use something like swaret, the upgrade process is very easy.Slackware drops GNOME, restores Mozilla
You're probably not going to like my method, but here goes: I keep a copy of the slackware -current tree, updated by rsync, and go through each directory in the slackware set, doing an 'upgradepkg *.tgz' in each one that I'm interested in upgrading. If I'm doing the 'A' set, I'll make sure I don't upgrade the 'aaa' packages, as those are meant for install-time use. I suppose you could consider it a very 'fast and loose' sort of upgrade method, but it's worked well so far, although one does have to go through and find and fix new configuration files (mostly in /etc/rc.d). I keep my Slackware systems pretty close to the vanilla install from Patrick (except for firewall rules et. al.) so things haven't been too rough.Slackware drops GNOME, restores Mozilla
In answer to the earlier question, I do the above upgrades online (without taking the system to runlevel 1) or rebooting.Slackware drops GNOME, restores Mozilla
Online is fine for one machine, but since I have 15 or 20 machines, I keep a local mirror. On each box, I just typeSlackware drops GNOME, restores Mozilla
./u
This is just a little script which goes to the appropiate directory on the local server and then executes the command
upgradepkg */*tgz
After that I usually reboot just to confirm that the bootloader still works.
Also if you reboot, you don't have to pick & choose which services to restart. I've gone for a few years now without needing a fresh install on any of those machines.
well upgrading slackware style is brilliant, because of simplicity:Slackware drops GNOME, restores Mozilla
so you have your cron running and syncing distro locally, then you can use swaret (also since 10.1 i guess, pat included slackpkg in extra dir, but i stick with swaret), just point swaret.conf to local mirror
We have multiple Slack machines at home. Like many others I use rsync to get a local -current mirror, from there all internal machines have access to slack-current via NFS. With Slack on NFS it is mostly a matter of doing an "upgradepkg */*.tgz" minus aaa_elflibs.Slackware drops GNOME, restores Mozilla
http://www.taickim.net/daniel/slackware-basics/html/pkgmg...