Index of /pub/slackware/source/gnome-2.18.3/
Vanilla Gnome 2.18.3 for Slackware 12.0
=======================================
State = final
This is a fully automated build process for Gnome-2.18.3 intended for
use on Slackware 12.0 (A fresh and full install).. Just cd into the
'gnome' directory and execute 'gnome.sh'. The script takes 2 arguements:
install and uninstall.
This is how "I" build gnome. It's a stripped down version that doesn't
even come close to what other GNOME offerings provide. However, the extra
directory picks up alot of slack in that regard. For the most part,
I'm making these scripts for myself and not anyone else. If you have the
same prefrences as I do when it comes to Gnome, then I think you'll be
happy with this.
My intent for Gnome on Slackware has always been simple. Build a
non-intrusive Gnome Desktop that holds true to the way Pat V. used to
build it. Straight up vanilla with no frills. Rampant package replacement
for tiny little enhancements or "bug-fixes" is unacceptable IMO... Bug fixes
need to originate from "proper" slackware channels, not from third parties.
If there is something wrong with a package listed in "stock-packages", the
best we can do is to email Pat and kindly ask him to fix it, or better yet,
provide a patch.
The only 2 packages that will get replaced on a stock Slackware system are
gnome-icon-theme and Firefox. Slackware is noted for not having a wide
array of multimedia apps (tho it seems alot better on 12.0) and I'm not
not willing to pick up the 'slack' with building them. Again, general
multimedia libs have no place in a GNOME offering but instead should
originate from proper Slackware channels. gst-plugins should still have
a fair ammount of support though if you've done a full install.
Here are the directories/files and their meanings:
stock-packages ------- These should already be installed by Slackware 12.
- If they're not, then install the official Slackware
- versions of them before you begin.
variables ------------ These are user defined variables. You can safely
- change any of them; as long as you understand what
- they mean and do... Make sure you look at this before
- you begin.
gnome-2.18.3.tar.bz2 - This is everything (minus the source) tared up. Just
- download this, extract it and cd into the 'gnome'
- directory and: sh gnome.sh install
- You do need an active internet connection for automatic
- source fetching.
contrib/ ------------- This is for people who may need to manually download
- the source code on another Unix based computer. As long
- as the source is in it's proper directory, the build
- scripts won't attempt to grab them.
gnome/ --------------- All the build scripts here will be run to build
- a "lite" version of gnome-2.18.3. Obviously, "lite"
- means everything that's in this directory and nothing
- else. I'm slowing succumbing to requests from users to
- add certain things. It's quickly moving past "lite" IMO.
gnome/gnome.sh ------- Parent run script which takes arguements. Call it
- solo to see the options AND important information
- concerning the 'extra' uninstall process.
gnome/Build-Order ---- This file is used by 'gnome.sh' to determine our build
- order. Don't delete anything from this unless your sure
- it's ok. If it's not in Build-Order, then it won't get
- built.
extra/ --------------- All the build scripts here will be run to build abiword,
- gnumeric, evolution and supporting dependencies. You must
- run 'gnome.sh' before attempting to build this directory.
extra/extra.sh ------- Parent run script which takes arguements. Call it
- solo to see the options.
extra/Build-Order ---- This file is used by 'extra.sh' to determine our build
- order. Don't delete anything from this unless your sure
- it's ok. If it's not in Build-Order, then it won't get
- built.
****** - If gnome.sh stops for any reason (it shouldn't), all you have to do is
*NOTE* - fix the cause of the error and run the script again. It will pick up
****** - right where it left off (trying to build the same package that errored).
- Same thing applies for the 'extra.sh' script.
-
- Also, if you want to rebuild a package of the _SAME_ $VERSION, for what ever
- reason, that has already been built/installed, do this:
- 1.) manually 'removepkg' on what ever it is you want to rebuild.
- 2.) delete the coresponding package name from /var/log/gnome-2.18.3/MANIFEST
- 3.) run the parent script again. (sh gnome.sh install)
- But that's ONLY if your rebuilding the same $VERSION number of said package.
- The script will automatically 'upgradepkg' where apropriate so don't worry
- about doing the above if your upgrading to a new version of whatever package.
- If you try and use this 'automatic' upgrade feature to go from 2.18.3 to
- 2.20.0, I can't guarantee that you'll have a stable Gnome-2.20.0 afterwards.
- Your more than welcome to try it tho. For that matter, I won't guarantee that
- just upgrading a few individual package versions within the same Gnome $RELEASE
- will result in a working Gnome. There is always a risk of breaking things when
- you upgrade. Use at your own discretion.
- For example, if you already have 2.18.3 installed and want to install 2.20.0,
- then your best bet is to run "sh gnome.sh uninstall" while you are in fluxbox
- or at the init3 console, reboot your machine and then run "sh gnome.sh install"
- on the new version. If you use ANY other method of upgrading, then your on your own.
See http://www.linuxquestions.org/questions/showthread.php?t=567725 for more info.
NOTE:
=====
You are more than welcome to modify and/or redistribute these
scripts, however, please do the right thing and don't slap
copyrights on them claiming ownership. I have a HUGE amount of
time invested in these scripts and such actions tend to irritate
me. :-) If you make changes, decide to redistribute them and
would like recognition for your efforts, make a seperate file
('changelog' perhaps?) which cites the original source location
(my web URL) and then put your name down along with any other
comments you'd like to make. I'd also request that you not
redistribute the binaries from these scripts for 2 reasons:
1.) Firefox and gnome-desktop are "officially" branded.
Because of trademark reasons, you are not allowed to do so
without permission from Mozilla(tm) and Slackware Linux(tm).
2.) This is meant to be a "compile from source" project.
a) You could inadvertently link a gnome package against something
that's not included in Slackware. It's just best to build it
from source.
That's all I ask. Thanks and have fun!
Jon Grosshart <jgrosshart@gmail.com>