Downloading From CVS - Revision history

Christian: layout fix/* Compiling a CVS version */

2009-08-17T18:55:18Z

layout fixCompiling a CVS version

← Older revision		Revision as of 18:55, 17 August 2009
Line 49:		Line 49:
	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:		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
	autoconf		./configure --enable-unstable-install more options
	./configure --enable-unstable-install more options		make
	make		su
	su		make install
	make install
	~~</verbatim>~~


	===Checkout the current stable branch===		===Checkout the current stable branch===

Fal7i at 16:02, 11 August 2009

2009-08-11T16:02:07Z

← Older revision		Revision as of 16:02, 11 August 2009
Line 1:		Line 1:
	= CVS IS DEPRECATED - BLUEFISH MOVED TO SUBVERSION =		= CVS IS DEPRECATED - BLUEFISH MOVED TO SUBVERSION =
			===Checkout latest SVN===
			<nowiki>svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/ bluefish-1.3.6</nowiki>
			====Compiling a SVN version====
			./autogen.sh
			./configure (./configure -h for help)
			make
			su
			make install

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

OlivierSessink at 22:10, 15 July 2009

2009-07-15T22:10:10Z

← Older revision		Revision as of 22:10, 15 July 2009
Line 1:		Line 1:
	~~Content~~-~~Transfer-Encoding: binary~~		= CVS IS DEPRECATED - BLUEFISH MOVED TO SUBVERSION =

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

Christian at 22:55, 26 October 2008

2008-10-26T22:55:00Z

← Older revision		Revision as of 22:55, 26 October 2008
Line 3:		Line 3:
	==Checkout a CVS version of bluefish using anonymous/developers CVS access==		==Checkout a CVS version of bluefish using anonymous/developers CVS access==

	This site shall help you working with [http://sourceforge.net/docman/display_doc.php?docid<code>14033&group_id</code>1]] and/or the [~~[CVS Book \|~~ http://lidn.sourceforge.net/ CVS \| http://www.gnu.org/software/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\" ].		This site shall help you working with [http://sourceforge.net/docman/display_doc.php?docid<code>14033&group_id</code>1] and/or the [http://lidn.sourceforge.net/ CVS Book] [http://www.gnu.org/software/cvs/ 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):		For anonymous checkout use the following command once (hit ''<ENTER>'' at the password prompt):

Christian: New page: Content-Transfer-Encoding: binary ==Checkout a CVS version of bluefish using anonymous/developers CVS access== This site shall help you working with [http://sourceforge.net/docman/displa...

2008-10-26T22:54:16Z

New page: Content-Transfer-Encoding: binary ==Checkout a CVS version of bluefish using anonymous/developers CVS access== This site shall help you working with [http://sourceforge.net/docman/displa...

New page

Content-Transfer-Encoding: binary

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

This site shall help you working with [http://sourceforge.net/docman/display_doc.php?docid<code>14033&group_id</code>1]] and/or the [[CVS Book | http://lidn.sourceforge.net/ CVS | http://www.gnu.org/software/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):

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

'''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 [http://bluefish.openoffice.nl/download.html 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:

<pre>
# 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
</pre>

As developer use:

<pre>
# 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
</pre>

Commit changes by using <code>cvs commit</code>.

====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:

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

As developer use:

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

This command is used to checkout the <var>bluefish_1_0</var> branch of the <var>bluefish-gtk2</var> module into a directory called <var>bluefish-1_0</var>. Use <code>cvs commit</code> 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 <var>release_x_y_z</var> in CVS. The latest release is '''release_1_0_1'''. To checkout the files belonging to a special release, use the following command:

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

As developer use:

<pre>
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
</pre>

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