For whatever work on SPEC files derived from the work we have done in Dude I went and created a Mercurial repository on opensolaris.org; it is the kde4- specs repository for the KDE project. You can access that one anonymously by following the instructions on the OSOL site, although they're a bit cryptic and hard to find. It might be easier to clone one of two clones:
https://solaris.bionicmutton.org/hg/kde4-specs https://solaris.bionicmutton.org/hg/kde4-specs-dev The former should be considered the "stable" repository, where only stable changes end up, such as complete upgrade paths. Both of these repos pull from the master repo on OSOL and neither pushes anywhere. The latter is an *open* repository which allows anonymous commits; this is an experiment on my part to see if we can get more community participation on the SPEC parts of the work. If you take a look at the specfiles, you'll find that they're awfully similar to the pspc files in Dude. What I will do, if this works out, is cherry pick patches from -dev and push to the more stable repo. For the time being, the OSOL repository *only* has FOSShier as a SPEC file in it. That's a totally minimal configuration, but I don't feel confident in pushing more to that place until we've had some testing. That said, one advantage of a Mercurial repo is it's trivial to get a tarball of the repo -- at least, it should be. I have not yet discovered where that's supposed to be found. But that means that for casual users, we can offer an easy-to-access tarball of SPEC files that will download and do all the stuff. Development is easy enough with Mercurial, *but*, and here we get to the subject of this mail, I had totally forgotten that there is no Mercurial on S10U5. imagine my surprise when I switched on the U45 and found no hg on it. So here's a very brief guide to getting it -- I hope someone else will put it up on techbase for me. - Download mercurial 1.0.2 from sunfreeware.com. Ignore the prerequisites. - Ungzip it and install the package with pkgadd -d mercurial-1.0.2-sol10- sparc-local (for instance) - Create the following script in your PATH somewhere: #! /bin/sh LD_LIBRARY_PATH=/usr/sfw/lib \ PYTHONPATH=/usr/local/lib/python2.5/site-packages/python \ /usr/local/bin/hg $* The LD_LIBRARY_PATH is to get libgcc_s.so from the right place and the PYTHONPATH is to read the packages from where mercurial installs them (while S10U5 has Python 2.4 somewhere else entirely). You will get one annoying warning per hg invocation, but it works fine otherwise in my admittedly limited testing. [ade]
