Dave's SlackBuilds

An annexe of The Daves Collective [ http://www.daves-collective.co.uk/ ]

The aim of this site is to provide an up to date collection of SlackBuilds in a few specialist areas of applications -- geospatial, photography and the Raspberry Pi. These SlackBuilds are mostly taken from SlackBuilds.org [ http://slackbuilds.org/ ] and Ponce's current branch on GitHub [ https://github.com/Ponce/slackbuilds ], but in many cases are updated for a more recent version. Thanks to the contributors and maintainers. See the SlackBuilds.org HOWTO [ http://slackbuilds.org/howto/ ] for details of how to use them. To verify the tarballs you'll need the GPG key [ http://slackbuilds/GPG-KEY ].

Prebuilt packages [ http://daves-slackbuilds.comlu.com/packages/ ] are available, if you value convenience over geek purity.

There's a whole page of notes and resources for running Slackware ARM on the Raspberry Pi [ http://daves-slackbuilds.comlu.com/raspi/ ].


The ChangeLog.txt [ http://daves-slackbuilds.comlu.com/slackbuilds/ChangeLog.txt ] isn't very informative yet :-)


This site won't just be a boring respository; there will be occasional rants about the difficulties of packaging other people's software.

For example, if you build spatialindex using cmake, it installs headers into a subdirectory that its own headers can't find. And there are projects (eg, darktable) that Debianite committers have broken supporting their bizarro new multilib setup. And there's the upstream tarballs (eg, hugin) from paranoid Fedorites that have nonstandard selinux headers in them. (Yes! I'd love four error messages for every file in the tarball, thanks!) And there are projects (eg, luminance-hdr) that untar to a random new subdirectory every new release.

Usually it's easiest just to fix this crap in the SlackBuild.

And then there's the joy of -Werror. The net is full of zombie developers with no self discipline who apparently can't otherwise sufficiently arouse themselves to fix their own warnings. This would be merely sad but harmless, if it wasn't for the policy of new releases of gcc to issue new warnings for old bad code; whereupon the upstream release suddenly won't build at all until some poor fool like me fixes the bad code or the bad Makefile/cmake/whatever.



Maintained by David Spencer, Baildon, West Riding of Yorkshire, aka idlemoor on GitHub [ https://github.com/idlemoor ] and 55020 on LinuxQuestions [ http://www.linuxquestions.org/questions/blog/55020-492011/ ]

This page was last modified on 2 July 2012

Copyright 2012 http://daves-slackbuilds.comlu.com/