Well, I've completely ditched the python directory and busted the python modules into their own dirctories, but other than that they are they same.

Oh.. your talking about the word new not the directory new, right? There are a few minor directory restructures but it's pretty much the same. I wish there was an easier way for you to grab the source. Putting them in the right directory is going to be worse unless you script it.

I've changed the online version of source.htm but I have to get to bed. It's 7:15am and I'm still up. If I didn't have today off I'd be royally screwed. I'll up load a new tarball tomorrow... or... today..

yes i am indeed talking about the directory name. sorry for the confusion. lolz.. its not biggie since i still get what i want in the end. and that is a GNOME build for slackware12.0 thanks!

Hi jon

A 7:15 am slumbertime wow!, dude you need a double-pay vacation after all of this :-)!

Before you head off though I have a couple of queries :-).

1. I rebuild my kernel pretty regularly which results in certain packages having to be rebuilt and/or re-installed. (Two examples are the ATI (fglrx) driver which have to be reinstalled bacause it stops working properly and the intel wireless card drivers that are built using a slackbuild which generates a kernel-specific slackpack.) Do you envisage that your Gnome build will experience such issues?

2. Is it possible for you to make available your "removed" directory (or was it named "not-included") containing the excluded Gnome sources and their buildscripts? Since I am experimenting with Gnome here for the most part, I may decide to test one or two of these omitted packages.

Cheers

Too late, I already slept and wok back up..

1.) No. There are absolutley no kernel modules in any of the gnome packages. They should just continue to work

2.) The extra build scripts that I didn't include in the scripts/ directory can be found here:
http://jaguarlinux.com/pub/DIY/source/gnome-2.18.3/

But, they should be inherently broken.
1.) I haven't used them in almost 2 years.
2.) they are different build scripts intended for my DIY build.

You would have to reorganize/change them if you wanted them to work with runme.sh and then you'd have to test them. If you just wanted to run them solo, you'd have to change "desc" to "slack-desc", change any libexecdir prefix, gzip info's and maybe tidy up a little more. But those are the same ones that I had in my earlier "not-used" directory. One of the reasons I ditched them because they were still straight up DIY and not Slackware.

For any Gnome packages that people might want that are beyond this project, It might be better to look elsewhere. I always seem to have too many things going on at once, I don't need to maintain build scripts I never use. Gnashley might have some nice build scripts floating around for Gnome. I'm not sure. Just be aware that I use --sysconfdir=/etc/gnome for anything gconf related. You'll have to pass that switch to get things in the right place (if applicable).

Brilliant m8 that will do very nicely indeed. Thanks once again for all the support.

Cheers

I just found iso-codes setting it's arch to i486 when it should have been noarch.. Again, I think we're down to nit picking now. I'm not going to keep a changelog. If you see the upload date has changed then I obviously changed something. Like I say, it should all be minor at this point.

Also, it's worth mentioning. 2 times out of the total 6 that I've run "runme.sh", the test suite for xml-simple bombed for some strange reason. If you imediately run it again, it'll complete with no errors and keep going to the next package. Haven't looked into it but I plan on it. I have a general idea of why it might be happening but it's not detrimental. If it happens, just hit the up arrow key and enter and ignore it.

i gave your scripts another run through and guess what, no errors at all and the menus are all there! thanks mate!

Sure. Everything does appear to be in working order.

Fixed Firefox's doinst.sh so it would find the librsvg plugin. I'll wait a week or so for feedback otherwise I consider it done right now...

Hi jon

Completed the build and all went fine. I am experiencing a problem with gxine though, it crashes Gnome and reverts to the login screen when I attempted to play an mp3. It is possible that I mixed up runme.sh scripts (the July 12th morning version for the evening version) while moving the manually downloaded sources into the directories. I don't know whether that may be a source of the problem.

A couple of other questions

1. Out of curiousity, I noticed that firefox was replaced with a similar version, any particular reason?

2. Some shortcuts and other deskttop items created on the KDE desktop appear on the Gnome desktop (but not vice versa) as "No Nome" (example hard disk devices) and produce an error when clicked. However if deleted from Gnome, they also disappear from KDE is there a way to prevent KDE items from showing on the Gnome Desktop?

Cheers

I'm not sure what's happening there but I would say it's not a gnome problem. Are you using a login manager of some sort? When you say it reverts to the login screen, are you talking about the init3 console? If it crashes X it's really a gxine/video driver/X problem, not gnome.

I'm using no login manager and just played some Kate Bush mp3's "with no problems..." :-) (once I installed seamonkey). I remember seeing a post about gxine crashing last week. You might want to investigate that. Honestly, it sounds like a slackware (or your system) problem. gxine has nothing to do with Gnome. None of your existing applications should be affected because they were compiled against Slackware, not any of my Gnome packages. There are other things that could be happening.. Does it crash under KDE?

It's not. runme.sh nor any of it's child scripts should affect gxine. Not unless you added gxine to the build list and rebuilt it.

Not sure I get you... What other version is there to install, unless we downgrade? The thing with Slackware's Firefox package is that it's a generic pre-built binary straight from mozilla head. Look at Pat's build script for it. It's actually an extract/repackage script. I build it from source so it contains the extra needed bits for yelp to compile against. For the most part, that's the only diff. I don't know what kind of .mozconfig mozilla uses so I'm sure there are differences.

Created by whom or what? Any .desktop files created by KDE need to follow desktop spec standards and vice versa. If they don't then there is going to be problems, I'm sure. What kind of desktop files are we refering to and what 'errors' do they produce? 'example' hard disk devices? Not sure I understand why "example' launchers for non-existent devices would be on the KDE or GNOME desktop. I just don't see it under Gnome. But ofcourse, deleting KDE is one of the first things I do...

If you give me some more info, I can install KDE and try to see what your talking about. But offhand, this sounds like a problem with the gnome and kde devs ignoring each others work and not following a unified standard. It's not really my goal to start patching gnome or kde so they respect each other.

As they should. Gnome and KDE share the same ~/Desktop directory. As for blocking KDE based desktop files from showing up in Gnome, I'm not sure... Again, they share the same Desktop/ directory so.... You could probably use a little trickery in your .xinitrc file...

I just installed KDE and there are a couple things I've noticed. This all boils down to KDE/GNOME integration which I have nothing to do with. I tried clicking on the "Home" desktop icon that KDE creates while I was under Gnome. You get something about /home/jon; no such command or whatever it says. If you open it up it says URL=$HOME for the exec bit. That doesn't do anything under Gnome. So now we have 2 home icons under gnome, one of which is broken, because KDE doesn't care how Gnome does things.

This is just one developer not respecting the other or rather ignoring the other. KDE creates it's Home and System Desktop files as .desktop files. So they show up under gnome. Gnome uses a gconf entry, I believe, so when your in KDE, you don't see Gnome's Home and System folders. Smart (and proper). When you click on your Home folder in Gnome, it actually has an executable to exectue. It'll issue a command of "nautilus uri://$HOME" or something like that. So, IF gnome's Home folder showed up in KDE to begin with, it would work. Instead, KDE is using a KDE only .desktop file to tell konquer to open $HOME.... Just sloppy IMO...

I'm not seeing any "No Name" sort of stuff on the KDE desktop. When I was in Gnome, I got into the Applications menu and did a "put on desktop" thing with a gnome program. Loged out and back into KDE and it's there on the desktop, name/icon shows and ececutes the program too.

Again, this just seems to be piss poor integration with GNOME and KDE and it's not my purview to change it. I'm not a Gnome or KDE developer so I'm not going to change anything with regards to that...

If there are any problems found with anything that get's built in the scripts/ directory, I most definitely want to hear about it and I'll try my best to resolve it, but this is really out of my hands. It's always possible I'm not understanding the circumstances of your problem correctly. If you can prove it's a faulty gnome package or missing configuration that should be happening within a gnome package, then yea... I suppose I'd be to blame like the earlier XDG problem. But right now, I'm gonna have to say "NMP"... Sorry...

Now, I did notice one problem that kind of concerns me. I'm not seeing any icons for KDE apps show in the Gnome menu (the names are there and they execute, just no icons). No icons are a big pet peeve with me. However, every single gnome related icon shows, so.... Initially, I want to say NMP, but this could be fixed, and indeed probably needs to fixed (but by whom is another matter). I'll look into it some more but again, these are existing KDE bits that were not built by me. I'll see if I can't figure out what's happening. Haven't looked into it yet. Creating an index.theme in respective KDE icon directories doesn't seem to help matters like it should. I have about 2 hours worth of KDE usage in the past 5 years. I just really dislike that DE so I'm not sure how it handles things. Not so sure I want to know to be honest.

jong357,
I've built Gnome now and it's working like a charm. Much appreciated! =) However there was a 404 error somewhere in the build. I can't recall which package it was, but I deleted it, along with everything already built from the "Build Order" list, and it went on.
Once again thanks!

-A

Oh... Looks like I'll have to track that down. Thanks. It seems to be unclear with some, no need to remove packages or do anything at all if the script fails. I've set it up so it will pick up right where it left off. All you have to do is run the script again and it'll try the same thing that just failed. All previous packages will be fine.

More specifically, you don't need to delete any thing from the "Build-Order" file. During the foor loop, I grep to see if the package got installed earlier. If it did, then we skip right over it and move on to the next package. So, you don't need to do anything but resolve the error and run the script again.

I am running it thru yet again to find that missing file you mentioned... Don't know what happened there. It built just fine the other day and I haven't made changes so it has to be someone's web server was down or something. I hope that package wasn't important.. You guys really shouldn't be doing that unless it's something stupid like gnome-device-manager... You never know what could break by skipping packages.

Glad it's working tho... Let me know if you find any problems (as long as it's not related to the missing package :-)

Hi, are there any ready binary packages to share with us?