Downloading From CVS

Content-Transfer-Encoding: binary

Checkout a CVS version of bluefish using anonymous/developers CVS access

This site shall help you working with 14033&group_id1 and/or the CVS Book CVS. Normally CVS (Concurrent Versions System) is used by the Bluefish developers, but we are also interested in users testing the development, giving us feedback about new features and possible bugs. So this site is written for both - users and developers. To understand the following commands or to get more information about using CVS, please read [[sf.net's \"Basic Introduction to CVS\" ].

For anonymous checkout use the following command once (hit <ENTER> at the password prompt):

cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bluefish login

Note: The sourceforge.net anonymous CVS server lags behind the development version by one day. Also the web CVS browser lags behind (up to 6 hours).

Checkout latest CVS

Warning: The CVS version is not always compileable. Most of the time the CVS version is the best Bluefish version available, but that is not guaranteed. The snapshots on the download servers are guaranteed to compile - but of course not guaranteed to be stable or bug-free. To checkout the latest CVS version of Bluefish or the Bluefish documentation use:

# for bluefish
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bluefish co bluefish-gtk2
# for the bluefish documentation
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bluefish co bluefish-doc

As developer use:

# for bluefish
cvs -z3 -d:ext:your_username@cvs.sourceforge.net:/cvsroot/bluefish co bluefish-gtk2
# for the bluefish documentation
cvs -z3 -d:ext:your_username@cvs.sourceforge.net:/cvsroot/bluefish co bluefish-doc

Commit changes by using cvs commit.

Compiling a CVS version

You can install any development version (snapshots, latest CVS) of Bluefish along with a stable copy. Therefor you have to use the --enable-unstable-install configure option. Bluefish will then be installed into /../bluefish-unstable (depending on your prefix). The user-directory is ~/.bluefish-unstable and the resulting binary /../bin/bluefish-unstable:

<verbatim> autoconf ./configure --enable-unstable-install more options make su make install </verbatim>

Checkout the current stable branch

The current stable branch is bluefish_1_0. For anonymous checkout use:

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bluefish co -d bluefish-1_0 -r bluefish_1_0 bluefish-gtk2

As developer use:

cvs -z3 -d:ext:your_username@cvs.sourceforge.net:/cvsroot/bluefish co -d bluefish-1_0 -r bluefish_1_0 bluefish-gtk2

This command is used to checkout the bluefish_1_0 branch of the bluefish-gtk2 module into a directory called bluefish-1_0. Use cvs commit inside the directory to commit changes to this branch.

Checkout a specific release

After a new release, all files belonging to this release are tagged with release_x_y_z in CVS. The latest release is release_1_0_1. To checkout the files belonging to a special release, use the following command:

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bluefish co -d bluefish-release-1_0_1 -r release_1_0_1 bluefish-gtk2

As developer use:

cvs -z3 -d:ext:your_username@cvs.sourceforge.net:/cvsroot/bluefish co -d bluefish-release-1_0_1 -r release_1_0_1 bluefish-gtk2

This command is used to checkout all release_1_0_1 tagged files of the bluefish-gtk2 module into a directory called bluefish-release-1_0_1. So you can always get the files belonging to a special release, even if the release was made years ago.