scc-logo

Downloads

Please refer to the scc FAQ, scc-win FAQ, scc-srv FAQ and the known limitations when you run into problems. Next to the released files, the latest source tgz files of scc, scc-win and scc-srv are also available for download.

Several people and companies contributed to SCC. Usage of these contributions to SCC is on your own risk. They give no warranty and are not responsible for problems caused by the modifications/extensions. Please test new releases of scc and scc-srv before deploying the software on your production systems.

As the download of scc-win contains software from putty, we copy the following warning:
"LEGAL WARNING: Use of PuTTY, PSCP, PSFTP and Plink is illegal in countries where encryption is outlawed. If in doubt, you should seek legal advice before downloading it. You may find this site useful (it's a survey of cryptography laws in many countries), but I can't vouch for its correctness."

MD5 sums of the downloads are available here. All scc/scc-srv packages/depots/rpms use the same code base. The following releases and downloads are available:

format scc scc-srv
source scc-1.23.185.src.tar.gz scc-srv-1.17.5.src.tar.gz
RPM scc-1.23.185-1.noarch.rpm scc-srv-1.17.5-1.noarch.rpm
package (Debian) scc_1.23.185-1_all.deb scc-srv_1.17.5-1_all.deb
package (Slackware) scc-1.23.185-noarch-1.tgz scc-srv-1.17.5-noarch-1.tgz
pacman (Arch Linux/Frugalware) scc-1.23.185-1.pkg.tar.gz scc-srv-1.17.5-1.pkg.tar.gz
package (FreeBSD) scc-1.23.185.FreeBSD.tgz scc-srv-1.17.5.FreeBSD.tgz
package (DragonFlyBSD) scc-1.23.185.DragonFlyBSD.tgz scc-srv-1.17.5.DragonFlyBSD.tgz
package (NetBSD) scc-1.23.185.NetBSD.tgz scc-srv-1.17.5.NetBSD.tgz
package (OpenBSD) scc-1.23.185.OpenBSD.tgz scc-srv-1.17.5.OpenBSD.tgz
PET package (PuppyLinux) scc-1.23.185.pet scc-srv-1.17.5.pet
pacman (ttylinux) scc-1.23.185-i486.tbz scc-srv-1.17.5-i486.tbz
tazpkg (slitaz) scc-1.23.185.tazpkg scc-srv-1.17.5.tazpkg
installp package (AIX) do it yourself do it yourself
SD-UX (HP-UX) do it yourself do it yourself
package (Solaris) scc-1.23.185.sunos.pkg scc-srv-1.17.5.sunos.pkg
Windows exe scc-win-1.8.11.msi Not available
Windows source scc-win-1.8.11.src.tar.gz Not available

The project is registered at Sourceforge. Access the repository here. Use the trunk directories of scc, scc-srv and scc-win for the latest and greatest.

Note that the data hierarchy of scc-srv is still present on a system after removing the software. You have to remove this hierarchy manually.


RPM

The software has been tested on CentOS6.4, CentOS7.0 and OpenSuse 12.3. Install release 1.23.185-1 of scc and release 1.17.5-1 of scc-srv with the following commands:

	rpm -U ./scc-1.23.185-1.noarch.rpm
	rpm -U ./scc-srv-1.17.5-1.noarch.rpm

When rpm complains that the package "is for a different operating system", you have to add the --ignoreos option to the command line.

Note that scc is run during the postinstall phase. In that phase, rpm cannot produce any data. This means that the snapshot does not contain any rpm data after a fresh install. This data is collected during the next (manual or scheduled) run of scc. On this run, the install of the new version is reported in the logbook.


Packages on Debian

The software have been tested on Debian 7.10 and Damn Small Linux 4.11. Install release 1.23.185-1 of scc and release 1.17.5-1 of scc-srv with the following commands:

	dpkg -i ./scc_1.23.185-1_all.deb
	dpkg -i ./scc-srv_1.17.5-1_all.deb

Depending on the configuration, dpkg can ask for confirmation to use the old or the new configuration files. As the only configuration files for scc reside in the newconfig directory and have to be activated manually, use the --force-confnew option to keep them up-to-date.


Packages on Slackware

Note: the package software of Slackware does not provide a preinstall script. Therefore you have to run scc manually before installing a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook.

The software has been tested on Slackware 14.0. Install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	installpkg scc-1.23.185-noarch-1.tgz
	installpkg scc-srv-1.17.5-noarch-1.tgz

To upgrade existing installations of scc and scc-srv, use the following commands:

	/opt/scc/bin/scc		# catch last changes 
	upgradepkg scc-1.23.185-noarch-1.tgz
	upgradepkg scc-srv-1.17.5-noarch-1.tgz

After removing scc or scc-srv, the data directories remain on the system and have to be removed manually.


Packages (pacman and pacman-g2)

The software has been tested on ArchLinux 2013. Install or upgrade to release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	pacman -U ./scc-1.23.185-1.pkg.tar.gz
	pacman -U ./scc-srv-1.17.5-1.pkg.tar.gz

Use the --noarch option for pacman-g2 (Frugalware).


Packages on FreeBSD

The software have been tested on FreeBSD 9.1 and 10.0. The install format does not work for FreeBSD 10, use the source install in that case. Install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	pkg_add ./scc-1.23.185.FreeBSD.tgz
	pkg_add ./scc-srv-1.17.5.FreeBSD.tgz

Remove the previously installed version of the software when upgrading. To upgrade scc from 1.5.37 to 1.23.185, use the following command:

	pkg_delete scc-1.5.37
	pkg_add ./scc-1.23.185.FreeBSD.tgz

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc. On this run, the install of the new version is reported in the logbook.


Packages on DragonFlyBSD

The software have been tested on DragonFlyBSD 3.4 and the installation is done in the /usr/pkg hierarchy. When upgrading from version 1.17.23, the existing logbook is ignored. Make sure that the package files are in the current directory and install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	pkg_add scc
	pkg_add scc-srv

Use the -u option to upgrade an already installed version of the software. When you remove the scc client, it runs one more time to collect data. This has to be done as the removal is also part of a regular upgrade. After the deinstall, the installation directory is removed. The data and configuration directories are still present.

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc. On this run, the install of the new version is reported in the logbook.

Note that the software has been build for DragonFlyBSD 3.0 on an x86_64 architecture. Installing it on other versions of DragonFlyBSD will succeed, but pkg_add will complain about the different OS version. When pkg_add refuses to install the software, use the -f option to force the install or download the source and generate the DragonFlyBSD packages with the scripts: dragonflybsd-gen-scc and dragonflybsd-gen-scc-srv.


Packages on NetBSD

The software has tested on NetBSD 6.1.1 and the installation is done in the /usr/pkg hierarchy. When upgrading from version 1.17.23, the existing logbook is ignored. Make sure that the package files are in the current directory and install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	pkg_add scc
	pkg_add scc-srv

Use the -u option to upgrade an already installed version of the software. When you remove scc, it runs one more time to collect data. This has to be done as the removal is also part of a regular upgrade. After the deinstall, the installation directory is removed. The data and configuration directories are still present.

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc. On this run, the install of the new version is reported in the logbook.

The software has been build for NetBSD 6.0 and i386 architecture. Installing it on other versions of NetBSD will succeed, but pkg_add will complain about the different OS version. To avoid this, you can download the source and generate the NetBSD packages with the scripts: netbsd-gen-scc and netbsd-gen-scc-srv.


Packages on OpenBSD

The software has been tested on OpenBSD 5.3 and the installation is done in the /usr/local hierarchy. When upgrading from version 1.17.23 (or earlier), the existing logbook is ignored. Make sure that the package files are in the current directory and install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	pkg_add scc
	pkg_add scc-srv

Add the -r option when upgrading an existing version.

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc.


PET packages on PuppyLinux

The software has been tested on PuppyLinux 5.7.1.

Note: the package software of PuppyLinux does not provide a preinstall script. Therefore you have to run scc manually before installing a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook. The warning from the client postinstall script about the missing lockfile can be ignored.

Install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	/opt/scc/bin/scc		# catch last changes 
	petget $(pwd)/scc-1.23.185.pet
	petget $(pwd)/scc-srv-1.17.5.pet

pacman on ttylinux

The software has been tested on ttylinux 16.1.

Note: the package software of ttylinux does not provide a preinstall script. Therefore you have to run scc manually before installing a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook. The warning from the client postinstall script about the missing lockfile can be ignored.

Pacman checks for the architecture in the name of the package. SCC consists of scripts only and can run on any architecture. Rename the package to your architecture and install. Install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	/opt/scc/bin/scc		# catch last changes 
	pacman --install ./scc-1.23.185-i486.tbz
	pacman --install ./scc-srv-1.17.5-i486.tbz

Before upgrading scc, the previous version should be run and removed with the -e option.

Note that diff and sort are implemented by busybox after a default system install. As scc requires these programs to produce the logbook, the logbook and its html-file are empty. Transferring these files to a fully functional scc-srv will produce the logbook and the html-file on the system running scc-srv.
On default installs of ttylinux the scc-srv software will not function. The package is added for those who install the required additional software: apache, sort and diff.


Packages on Slitaz

The software has been tested on Slitaz 4.0. Both scc and scc-srv packages in slitaz format depend upon diff-utils and coreutils-file-sort to replace the limited busybox functionality for diff and sort. Install or upgrade to release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	tazpkg install ./scc-1.23.185.tazpkg
	tazpkg install ./scc-srv-1.17.5.tazpkg

Installp packages on AIX

To generate these packages, you require /usr/sbin/mkinstallp from bos.adt.insttools to run installp-gen-scc and installp-gen-scc-srv. Then install or upgrade to release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	installp -a -d ./scc.1.23.185.1.bff scc
	installp -a -d ./scc-srv.1.17.5.1.bff scc-srv

SD-UX depots on HP-UX

To generate these packages, you require swpackage to run hpux-gen-scc and hpux-gen-scc-srv. Then install release 1.23.185 of scc and release 1.17.5 of scc-srv with the following commands:

	swinstall -s $(pwd)/scc-1.23.185.hpux.depot scc
	swinstall -s $(pwd)/scc-srv-1.17.5.hpux.depot scc-srv

To register both depots, use the commands:

	swreg -l depot $(pwd)/scc-1.23.185.hpux.depot
	swreg -l depot $(pwd)/scc-srv-1.17.5.hpux.depot

To copy both products to an existing depot, use the commands:

	swcopy -s $(pwd)/scc-1.23.185.hpux.depot scc @ /your/depot
	swcopy -s $(pwd)/scc-srv-1.17.5.hpux.depot scc-srv @ /your/depot

Packages on Solaris

Both scc and scc-srv require the XPG4 software (SUNWxcu4) on the system to work correctly. The packages can be installed on sparc and intel architectures. The software has been tested on Solaris 10. Install release 1.23.185 of scc and release 1.17.5 of scc-srv in the Global zone with the following commands:

	pkgadd -G -d ./scc-1.23.185.sunos.pkg -a none scc
	pkgadd -G -d ./scc-srv-1.17.5.sunos.pkg -a none scc-srv

During the installation, you will be asked whether the installation-scripts should run. Use the following admin-file and the -n option for pkgadd to fully automate the installation process.

	basedir=default
	mail=
	runlevel=nocheck
	conflict=nocheck
	setuid=quit
	action=nocheck
	partial=nocheck
	instance=overwrite
	idepend=nocheck
	rdepend=nocheck
	space=nocheck

Note that installs in a zone will fail for release prior to S10_73. Use pkgtrans to transfer the contents of the pkg-file to a directory structure and then install from the directory.


Source

Use this method of installation when the native install format for your OS is not available. To install scc from source, use the following commands:

	# transfer src.tar.gz to your host
	tar zxf scc-1.23.185.src.tar.gz
	cd scc-1.23.185
	./scc-install
	cd ..
	rm -rf scc-1.23.185.src.tar.gz scc-1.23.185

To install scc-srv from source, use the following commands:

	# transfer src.tar.gz to your host
	tar zxf scc-srv-1.17.5.src.tar.gz
	cd scc-srv-1.17.5
	./scc-srv-install
	cd ..
	rm -rf scc-srv-1.23.185.src.tar.gz scc-srv-1.23.185

The tarball contains scripts to generate all depots, rpms and packages after modifying the source-files. Refer to the relocate script when you want to install the software in non-default directories. Be sure to edit this script before using it and do not mix default and relocated packages on a single system.


Windows executable

Note that the 1.7 MSI file does not uninstall 1.6 installs. Use the following steps to upgrade from release 1.6.20 to 1.7.57:

  • run your current schedule of scc-win
  • uninstall release 1.6.20
  • install release 1.7.57
  • run your current schedule of scc-win

The download is 32-bit MSI installing the software in /Program Files (x86)/SCC that was built by means of the WIX toolset.

The server-part of scc is not available for Windows, only the client-part. The client software has been tested on Windows 7 and 8 and is known to run on earlier Windows versions. Note that you need additional software on your Windows systems. The software requires perl. We tested the software with ActivePerl from Active State.

Note: the MSI does not provide a pre- and post-install. Run your own schedule of scc-win before and after the install of a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook(s).

Note that after the first install of the client-software, the scheduling of scc-win has to be configured. You need to run scc-win with sufficient privileges. Running the software as domain administrator, even enables you to install the software on a single system and retrieve data from all other systems in your domain. Refer to the documentation of scc-collect for an overview of all options you can use to indicate what systems to collect data from.


Windows source

Unpack the archive to retrieve the build environment of the Windows client of SCC. You can adjust the source and use the WIX toolset via script msi.bat to generate the new MSI.


Do It Yourself

The software is not (yet) generated in this package format as we do not have access to this platform. The package generation has been scripted and is available in the source package. Download and unpack the source package and activate the script generating the software in the missing package format. The script will report any missing utilities.


MD5 sums

Here are the size in bytes and the MD5 sums of all the downloads:

     scc_1.23.185-1_all.deb                  335800 82169d8698b0ca6cfc486ad274c5eafe
     scc-1.23.185-1.noarch.rpm               347456 cf02bda605166279aa667067a080c510
     scc-1.23.185-1.pkg.tar.gz               333363 c7c5a03d70b628708bd456a9e0428631
     scc-1.23.185.DragonFlyBSD.tgz           335256 eaca40241b16532eb4c70b9c85dae806
     scc-1.23.185.FreeBSD.tgz                335221 ff75997810495cde04c73f8e471c46c2
     scc-1.23.185-i486.tbz                   250208 efb07e1d1a8fbe8ff56f72027a22ddf3
     scc-1.23.185.NetBSD.tgz                 335259 4c8c0ea717759c6ad92f4babf9a1d370
     scc-1.23.185-noarch-1.tgz               330882 c94c896dd6baf8baccce194190e2151f
     scc-1.23.185.OpenBSD.tgz                335874 cc5d2309902655dd4735c39c9aacc8eb
     scc-1.23.185.pet                        333129 3d7c903e2660075483533b37c768fb12
     scc-1.23.185.src.tar.gz                 350719 9200409dbf7bcc19f716027340852aa7
     scc-1.23.185.sunos.pkg                 1290240 9f8e1489e563a6ebabaef53ae1de8016
     scc-1.23.185.tazpkg                     291840 c7450858c3deb375256adb8ae68a41d9
     scc-srv_1.17.5-1_all.deb                242570 f3b6d5645dd8aa1faf1bdd045951c43e
     scc-srv-1.17.5-1.noarch.rpm             264591 497e7d2453516524d25e1a19bfd0460d
     scc-srv-1.17.5-1.pkg.tar.gz             239613 16dd74563f5477f28eda37957a7601a3
     scc-srv-1.17.5.DragonFlyBSD.tgz         241703 7de82f66c17c5cd8af45cf65b71fed25
     scc-srv-1.17.5.FreeBSD.tgz              241665 59d4ff61328538883c4138dbcbf5d6ff
     scc-srv-1.17.5-i486.tbz                 153905 b97a2c4ef6632d1a461314c9b4adbd90
     scc-srv-1.17.5.NetBSD.tgz               241689 0870d68c7952d1e6fa608cb3f04812ab
     scc-srv-1.17.5-noarch-1.tgz             237273 05fd4215f9d947cfb32445d9b9deba6d
     scc-srv-1.17.5.OpenBSD.tgz              244156 f500c9e835a2eaf1cfd6b15fe94b9871
     scc-srv-1.17.5.pet                      239397 57ea7019e7bcdded069a01e9073c759c
     scc-srv-1.17.5.src.tar.gz               253756 63ca9daf771f195475d037d1c9e0cf21
     scc-srv-1.17.5.sunos.pkg                971264 066ff28f34dbfa4f8da1f1cf43c035d0
     scc-srv-1.17.5.tazpkg                   219648 454374a2ac2d4cac8f5b0433fd629f02
     scc-win-1.8.11.msi                     2277376 c6c1e18a03193bcc9a028773c86c726d
     scc-win-1.8.11.src.tar.gz              2248724 de7cf85c0f57303b8cdf87ee53232a81

Intro News Architecture Download Support Credits Others