It does work well. Tuche. Having some problems getting GConf to keep my altered settings tho. I was upgrading from stock 2.6 Gnome. If your so inclined, maybe you might want to expand a little on the upgrade process, like whether or not to remove your ~/.* folders associated with the original Gnome. I'll iron it out. Thanks again!

First and foremost, thanks for your collaboratioj with this packages, I feel most tempted to grab them and install them, but, I always have had the curiosity on compile Gnome, so, if it is not bold to ask, could you Linuce, or any one else, point me to a good tutorial, or give me recommendations on how to compile Gnome? I will be forever grateful.

Thanks a good day.

Thanks for the work Linuce
If I can help you, you can let me know on that forum or
at the forum of Linux Trois-Rivieres
http://linuxtr.ampr.org


A note if you have some problems with the gnome-kerboard-properties, do the following.

First method

cd /usr/X11R6/lib/X11/xkb/symbols/pc/
ln -s /usr/X11R6/lib/X11/xkb/symbols/* .

Second method

Edit /etc/X11/xorg.conf

Changed the line:

# Option "XkbDisable"
to

Option "XkbDisable" "Yes"

Restart the Xserver if you use the second method.

Richard

When I built GNOME 2.6 I used the BLFS guide.
Most of the instructions for 2.6 shoud be applicable to 2.8. You may have to improvise a little.

The automated updated tools I've tried (swaret and slackpkg) don't like the naming convention you've used for your packages. In both cases, they want to 'upgrade' your Gnome packages to older versions from the official repositories, instead of ignoring them.

As far as I know, the naming convention I have used is the standard one : package parts are read from right to left, each part being separated by a dash sign ("-"). Note that a package which already exists in Linux Slackware 10.1 keep its name. So the "problem" probably comes from the non-standard tools you use. Also note that there is a README.txt which is supposed to be read : please, read it as it describes the only one way to properly installs these GNOME 2.8.2+ packages by using official package managment tools provided with Linux Slackware. As I'm kind enough, I will show you the two first, non-empty lines of this file :) :

I have upgraded my Gnome packages following your prescribed method - this is not about that, nor my ability to read simple text files.

I refer to your naming convention of <package name>.linuce.tgz - which *does* break the tools, non-standard or not as you call them.

The alternative method would be to follow the LinuxPackages.net form of <name>-<version>-<arch>-<revision><packager initials>.tgz, which does not break such tools (no . between revision and initials/your name).

Yes, it would probably be wiser to use initials, but as long as current naming scheme does not break official package managment tools, I think it's "standard". I will probably change this to use initials instead of the my internet nick (which is a anagram of my real name).

In fact, I use "linuce" so that when I want to get rid of non-official Slackware packages, I just run : and I get a clean Slackware system (as I don't install third party packages, except those I have built by myself) after reinstallaing missing ones with :

Using the initials or your name isn't really the problem - it's the period/full stop/. you put between the revision number and your name that throws the tools into disarray.

Slackpkg may not be completlely 'official', but it is in /extra with 10.0 and 10.1