[tools-discuss] Distributed SCM evaluation packages.
Frank van der Linden
Frank.Vanderlinden at Sun.COM
Thu Jan 26 06:48:20 PST 2006
Hi folks,
After looking at Glynn's preliminary packages, getting an idea how it
should be done, I've packaged up the initial distributed SCM candidates
as listed by Stephen.
They are available for download at
http://www.opensolaris.org/os/community/tools/dscmdownload/
The packages are available for x86 and sparc where needed, and as
architecture-neutral package where possible.
Since I really wanted to follow Stephen's suggestion of only installing
in /opt/dscm, to keep things clean, a few things should be noted:
* Everything is installed in /opt/dscm
* For one of the packages, Python 2.4 was needed. This was not available
under /usr/sfw, nor as a Blastwave package. So I created a DSCMpython
package for Python 2.4.2, which lives under /opt/dscm, and only has
"python2.4" as an executable, so that you may safely add /opt/dscm/bin
to your path without having a conflict with your other Python installation.
* Other Python packages in this set were configured to use this version
of Python, for consistency.
* For Perl packages (SVK), all Perl modules were installed under
/opt/dscm/lib (/site_perl, /i86pc-solaris-64int), and a wrapper script
is used to make svk find the right modules, by setting the PERL5LIB
environment variable.
* Since the number of total Perl module dependencies (that were not
found in the default Perl install) for SVK amounts to 44 packages, I
bundled them into one big DSCMsvk-perl-depends-<arch> package. Really
only a few of them are architecture-specific since they have shared
objects, so this can be done more correctly in the future if anyone
cares enough.
Also note that despite its name, the main Mercurial program is called "hg".
Source is provided for all packages at the URL mentioned above.
If you find any problems that seem to be related to how things were
packaged up, let me know.
- Frank
More information about the tools-discuss
mailing list