packaging gnome
 

dear all,

i am slowly thinking of start packaging gnome for slamd64, however before i take boring and wrong steps i'd like to know your experience.

what would you suggest to do such a thing, i believe of course stuff like gargnome are completely out of the question.

...any ideas?

thanks,

aj.

Be prepared to pull your hair out ;)

--Shade

I made build scripts for all of 2.8.3... They work wonderfully. They're not 'true" .SlackBuild scripts because they don't build the package at the end. I prefer to do that manually once I visually inspect the package to make sure all is well. But, yea.... Get ready to waste some time. I'd say the key is to make sure you update key things via your doinst.sh's... If you don't, you'll have a hosed Gnome. For example, a package that is designed to work with scrollkeeper, you have to have this in the doinst.sh
There are several others as well besides scrollkeeper. I'm pretty sure these are all of them:

1. scrollkeeper-update
2. gconftool-2
3. update-desktop-database
4. gtk-update-icon-cache
5. gdk-pixbuf-query-loaders

If you use those where required, you'll end up with a tight Gnome desktop right from the get-go....

if only i had any :)

will check these out. as the total beginner i'm in this i actually do not even know where to start from, these might be a good place to. thanks.

Sure... If your really stuck I can tarball some or all of my scripts/doinst.sh's for you to look at. Why re-invent the wheel is my philosophy.... Actually, I took LiNuce's doinst.sh's and made them my own with a bit of formatting... No offense tho, I shuddered at his build scripts.... Ugh.... So I made my own scripts that are just like Pat's except I remove the ARCH/BUILD variables from up top and remove the very end makepkg line... Now that I know they all work flawlessly, I kind of wish I would have left that stuff in there... Oh well.

You might want to have a look at the GSB scripts as a starting point.

i have a feeling that this is way out of my hands.

looked at the scripts: it's 230 KB of compressed scripts of which i wouldn't know where to put my hands on to begin.

i'd feel like installing slamd64 (which is without gnome) and then building it up, manually, to see how it works. then, encode all this into a script.

do you know how to build manually gnome from the start? i downloaded all the source tarballs available here.

any additional help more than welcomed.. once i succeed in building gnome manually i'll start building scripts for it...

thank you,

aj.

found this, valid for gnome 2.8:

External Dependencies
• pkg-config, available at http://www.freedesktop.org/software/...-0.15.0.tar.gz
• The Xft2 and fontconfig family of libraries, available at http://fontconfig.org/. Note that while these libraries are available as part of XFree86 4.3, the newer versions from fontconfig.org are highly recommended.
• FreeType 2.0.9 or greater, available at http://www.freetype.org/
• docbook-xml [docbook dtd 4.1.2]
• docbook-xsl [docbook xsl stylesheets]
• shared-mime-info
• hicolor-icon-theme

Development Library dependencies
• libpng
• libjpeg
• libtiff
• XFree86
• libpopt
• libbbz2
• zlib
• libfam
• libgpg-error
• libgcrypt
• libtasn1
• opencdk
• gnutls
• libgsf
• libcroco
• mozilla

GNOME 2.8 Installation Order
• libxml2
• libxslt
• gtk-doc
• glib
• libIDL
• ORBit2
• intltool
• libbonobo
• pango
• atk
• gtk+
• gconf
• desktop-file-utils
• gnome-mime-data
• gnome-vfs
• audiofile
• esound
• libgnome
• libart_lgpl
• libglade
• libgnomecanvas
• libbonoboui
• gnome-icon-theme
• gnome-keyring
• libgnomeui
• startup-notification
• gtk-engines
• gnome-themes
• scrollkeeper
• gnome-desktop
• libwnck
• libsoup
• evolution-data-server
• gnome-panel
• gnome-session
• vte
• gnome-terminal
• libgtop
• gail
• libxklavier
• gnome-applets
• metacity
• librsvg
• eel
• nautilus
• gnome-control-center
• gtkhtml2
• gnome-doc-utils
• yelp
• bug-buddy
• libgnomecups
• libgnomeprint
• libgnomeprintui
• gtksourceview
• gedit
• eog
• ggv
• gconf-editor
• gnome-utils
• procman
• gstreamer
• gst-plugins
• gnome-media
• nautilus-media
• gnome-netstatus
• gcalctool
• gpdf
• gucharmap
• nautilus-cd-burner
• zenity
• at-spi
• libgail-gnome
• gnome-speech
• gnome-mag
• gnopernicus
• gok
• epiphany
• gnome-games
• gnome-user-docs
• file-roller
• gnome-system-tools
• gnome-nettool
• vino
• dbus
• hal
• gnome-volume-manager
• gal
• gtkhtml
• evolution
• evolution-webcal
• gnomemeeting
• libsigc++
• glibmm
• gtkmm
• libgnomemm
• libgnomecanvasmm
• libglademm
• libgnomeuimm
• gnome-vfsmm
• libgtk-java
• libgconf-java
• libglade-java
• libgnome-java
• Glib (perl)
• Gtk2 (perl)
• Gnome2 (perl)
• Gnome2-Canvas (perl)
• Gtk2-GladeXML (perl)
• Gnome2-VFS (perl)
• Gnome2-GConf (perl)
• pygtk


...if i install every package in THIS order will it work?

It's supposed to... For some reason, I don't trust that page. Following their build order twice before didn't work for me if I remember correctly. You also don't need some of that stuff actually. This is how I do it. 2.8.3 runs great in this order.

There are a few packages that need to be built before any of that but you should have them already.. Like:

• libpng
• libjpeg
• libtiff
• XFree86
• FreeType 2.0.9 or greater
• Xft2 and fontconfig

My documentation isn't the best though so you should probably try the Gnome list. I just noticed I don't have "docbook-xml-4.3" listed... :( I must have been on a roll and forgot to insert that one.... It's requirements are libxml2, so it's perfectly safe to put that one right under libxml2..... You get the idea. Just a huge dependency chain. There are also some on the Gnome list that you don't need. Like docbook-xsl.. I also don't use dbus or gtk-doc. Why use gtk-doc when most of the programs already make their own gtk docs? I could go on and on and on about the idiosyncrasies of building Gnome.

Those are the versions I used months ago. There are updated packages for alot of them. Like GTK2 for example. fam and portmap are extras. I just wanted Nautilus to automatically update when changes were made... Well, anyway...

wow!

thank you jong!

this looks precious. what do you go about this? did you individually change .config files before makeinstalls or you went by default?

i'm looking forward to installing slamd64, though i'll have to say bye to slack for some time... and before i do this i want to have the correct information on how to proceed.

it's really incredible how things are sometimes organized with gnome. they spend 2 months to invert 'cancel' with 'ok' button, and then on 2.10 they take away menu management! talking about idiosyncrasies...

it seems the same is done here. why the hell such a simple information such as this one of a package building order is impossible to find anywhere... why! this really is mistery to me. i feel like programming my very own gnome panel, these kind of feeling. oh well.

back to the point.

you seem to be saying that

• ibpng
• libjpeg
• libtiff
• XFree86
• FreeType 2.0.9 or greater
• Xft2 and fontconfig

correspond therefore to what gnome devels are stating.

would this seem ok for you? i install the above (if not yet installed, or maybe i'd figure an upgrade) and then install your list?

then all i'd have to do is build a package out of every compile i do on a 64 arch, and build a script that will install them on a target machine in the same order... seems cool?

Um, not sure what you mean there.. I didn't have to edit any makefiles if thats what you mean... I set MAKEOPTS, CFLAGS and CXXFLAGS globaly in /etc/bashrc. That way I don't have to worry about incorporating them into each build script. I still do customized ./configure options where appropriate in the build scripts. After the script is done I 'cd' into the package directory and then run makepkg and then installpkg... Then move on to the next one... You don't have to make build scripts of course...
I know... I'm extremly unhappy with the direction Gnome has been going. 2.8.3 may very well be my last build...

Right... Those should be installed first.

Right... Thats a good idea. It's about the only thing I have left to do that I've been shirking, is making an install script... I haven't formatted since I built/installed the packages... No need for an install script now since I installed each one right after I built them. I'll get around to it sooner or later, I'm sure.

I was kind of taken with LFS's approach to Gnome. eg - using:
Pretty cool IMO... So, whatever prefix you give Orbit2, thats going to be the prefix using the above. I installed Orbit2 in /usr, like Gnome packages traditionally are. So, really, thats the same thing as:

I also liked the idea of clumping all the sysconfig files into /etc/gnome, not just /etc
whew.... ALSO.... :D I was fairly impressed with LiNuCe's doinst.sh's as I've said so there are some tricks to getting schemas in place and registered upon install (along with the others that I listed a couple posts back). Here's my file-roller build script. This shows you how schemas are handled with the package.
Here is the coresponding doinst.sh:
The main thing is to know when to use what command for which doinst.sh... :-) Like I said, If you do that, you have a smooth running Gnome.

again, thank you.

i will keep these scripts for reference.

i also contacted the GBS team (which is packaging gnome 2.10 for slackware) and they got back to me for this idea of packaging gnome 2.10 for slamd64.

they will send me detailed instructions on how they do it during this weekend.

i will then give it a try and hopefully come up with something for all of you 64 slackware archers out there.

hopefully this IS interesting some one :) well at least it is interesting me.

any comments still more than welcomed,

cheers,

aj.