Dropline with Slack 12

folkenfanel · 07-04-2007, 09:07 PM

Hi.

As I said, I am polishing my build scripts (specially the post-installation stuff). I make my own Slackware-based distro for my personal use, so I like to compile some things, make .tgz packages, make them into series and add them to my installer CDs. (take a look at "Cooking up some Slackware - CUSS). So far, I am figuring out how to make more efficient the part that automatically generates the default gconf entries under /etc/gconf/gconf.xml.defaults.

As soon as I think they are (the SlackBuilds) "stable" enough, I will make them public.

Quote:

Do your scripts automatically download all the required packages & dependancies?

No, I do NOT download the packages and dependencies automatically, BUT I do keep a list of those dependencies and the places where they can be found. Don't fear, there aren't too much.

I am planning to make two versions: one with every package built stand-alone and the second (the way I like it) with "cousin" packages merged into big packages (this is, the series they are built of from: gnome-platform, gnome-bindings, etc). I don't like having hundreds of packages wandering inside /var/log/packages.

I focused on building a MINIMAL install as close as possible to the original sources. (the way GNOME was built when it was officially built in Slackware). I think perhaps that's why it didn't cost me so much - I mean, finding extra dependencies for extra software.

I still have to figure how to correctly compile epiphany and yelp.

Thanks a lot for your interest. It is encouraging.

folkenfanel · 07-04-2007, 09:12 PM

http://download.gnome.org/platform/2.18/
http://download.gnome.org/desktop/2.18/
http://download.gnome.org/bindings/2.18/
http://download.gnome.org/admin/2.18/
http://download.gnome.org/devtools/2.18/

You can find most sources there.

b3rx · 07-04-2007, 09:51 PM

you mentioned that you also got some packages at freedesktop.org that was needed. may i know what those packages are?

folkenfanel · 07-06-2007, 01:29 PM

Code:

freedesktop-utils: icon-naming-utils (backwards compatibility with icon themes)
freedesktop-utils: liboil (develop/maintain code for MMX/SSE/Altivec extensions)
freedesktop-utils: libxklavier (utility library for X keyboard-related projects)
freedesktop-utils: system-tools-backends (DBus interface for system configuration)

You need XML::Simple to compile icon-naming-utils.

folkenfanel · 07-06-2007, 01:30 PM

As I said, it runs but it's still "beta"

jong357 · 07-06-2007, 08:22 PM

Quote:

Originally Posted by folkenfanel

Hi.So far, I am figuring out how to make more efficient the part that automatically generates the default gconf entries under /etc/gconf/gconf.xml.defaults.

folkenfane, have a look at my gnome-2.18.3 directory if it will help you with stuff like that. I've been building gnome for quite a few years and have never had a problem with my doinst.sh's..

http://jaguarlinux.com/pub/DIY/source/gnome-2.18.3/

I started to convert those build scripts to true .SlackBuilds (for use on 12.0) but I've lost some motivation. What's in that directory is for my DIY build which uses a slightly modified pkgtools. But they'll work on Slack with a global s/install\/desc/install\/slack-desc/... No use of /usr/libexec and no gziped info's but other than those 3 things, they are ready for Slack.

Also, I'm not sure there is a way around the yelp problem besides building your own firefox. Dropline does it for the same reason I imagine. The generic binaries that Pat uses straight from mozilla don't contain the necessary files to build yelp against.

I've also never had a problem with epiphany but I ussually don't build it anyway because I use Firefox.

zborgerd · 07-11-2007, 12:15 PM

Quote:

Originally Posted by jong357

folkenfane, have a look at my gnome-2.18.3 directory if it will help you with stuff like that. I've been building gnome for quite a few years and have never had a problem with my doinst.sh's..

http://jaguarlinux.com/pub/DIY/source/gnome-2.18.3/

I started to convert those build scripts to true .SlackBuilds (for use on 12.0) but I've lost some motivation. What's in that directory is for my DIY build which uses a slightly modified pkgtools. But they'll work on Slack with a global s/install\/desc/install\/slack-desc/... No use of /usr/libexec and no gziped info's but other than those 3 things, they are ready for Slack.

Also, I'm not sure there is a way around the yelp problem besides building your own firefox. Dropline does it for the same reason I imagine. The generic binaries that Pat uses straight from mozilla don't contain the necessary files to build yelp against.

I've also never had a problem with epiphany but I ussually don't build it anyway because I use Firefox.

Yeah. That's why we include our own Firefox build still even after Slackware got one officially a few releases ago. I believe that Freerock had another solution of including a few gtkembedmoz libraries, which is an option that you guys may want to consider.

As for the next stable Dropline release (since some have asked): We're working on it. Lots of changes are going on, but we will be targeting Slackware 12.0. I have hopes we can have a beta or pre-release in the next week or two. 2.18 is available for Slackware 11.0, but with the uncertain release date of 12.0, and a few unsolved issues, we never formally have taken 2.18 out of pre-release. I think that most people will find that it is quite good aside from the system-tools-backends problems.

zborgerd · 07-22-2007, 11:43 PM

We've posted an announcement on the homepage about the beta:

http://www.droplinegnome.org/

The new Dropline GNOME for Slackware 12.0 replaces only 8 Slackware packages in the beta build. We are trying to strip out 2 or 3 more, but then we lose features (proper HAL mounting support, gecko for the browsers (help, rss, etc), and exchange server support in Evolution, a bug-free VTE and a few other important things. It's a huge step, in my opinion. Full list here:

http://forums.droplinegnome.org/viewtopic.php?t=4739

Here is a screenie. We should be able to call 2.18.3 complete this week.

http://zborgerd.droplinegnome.org/sc...woEighteen.png

I would say that, aside from a few outstanding package rebuilds and a few fixes as noted in the forum thread, it's ready for the public and most of the bugs will be worked out tomorrow.