Introduction to CVS - Revision history

imported>Thymo: Added notice

2017-01-26T16:55:12Z

Added notice

← Older revision		Revision as of 16:55, 26 January 2017
Line 1:		Line 1:
			{{Attention \| message=NASSP has moved version control over to GitHub. More information can be found [http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=2864.0 here].}}


	This introduction tries to provide step-by-step instructions to the '''Project Apollo CVS repository''' at SourceForge. It's no comprehensive introduction to CVS or SourceForge. For further informations please use the following links:		This introduction tries to provide step-by-step instructions to the '''Project Apollo CVS repository''' at SourceForge. It's no comprehensive introduction to CVS or SourceForge. For further informations please use the following links:

imported>Tschachim: Removed TortoiseCVS version waring as the latest version seems to work fine

2012-04-03T13:17:06Z

Removed TortoiseCVS version waring as the latest version seems to work fine

← Older revision		Revision as of 13:17, 3 April 2012
Line 11:		Line 11:
	We recommend '''[http://www.tortoisecvs.org TortoiseCVS]''' as client, so first of all please download and install it. You will also find some instructions especially for SourceForge in the TortoiseCVS help. We also recommend to take the time to read the "Using TortoiseCVS with SourceForge" chapter and the "Using Pageant to avoid having to enter the SSH password every time" chapter in the help file and to use Pageant.		We recommend '''[http://www.tortoisecvs.org TortoiseCVS]''' as client, so first of all please download and install it. You will also find some instructions especially for SourceForge in the TortoiseCVS help. We also recommend to take the time to read the "Using TortoiseCVS with SourceForge" chapter and the "Using Pageant to avoid having to enter the SSH password every time" chapter in the help file and to use Pageant.

			You need a SourceForge login to be able to commit your changes to SourceForge and you have to be added as a developer to Project Apollo by a project administrator. So please make a login for yourself and post an informal request with your login (UNIX name) included that you wants to be added at the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum].
	{{ Attention \| message=It looks like the latest TortoiseCVS version is '''not working''' with the SourceForge CVS server, so we strongly recommend to use the latest known working version instead, [http://downloads.sourceforge.net/tortoisecvs/TortoiseCVS-1.8.29.exe TortoiseCVS 1.8.29].


	You need a SourceForge login to be able to commit your changes to SourceForge and you have to be added as a developer to Project Apollo by a project administrator. So please make a login for yourself and post an informal request with your login (UNIX name) included that you wants to be added at the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum].}}


	If you use CVS the first time you can practice the basic CVS operations with the test module (named "test"). Do the checkout as explained below, but use "test" as module. You'll get some test files you can change as you like to get familiar with CVS.		If you use CVS the first time you can practice the basic CVS operations with the test module (named "test"). Do the checkout as explained below, but use "test" as module. You'll get some test files you can change as you like to get familiar with CVS.

imported>Swatch: /* Comments and remarks */

2010-12-12T18:55:41Z

Comments and remarks

← Older revision		Revision as of 18:55, 12 December 2010
Line 86:		Line 86:
	* There is no NEP support at the moment so please do NOT install NEP in your development folder (and of course no other add-on).		* There is no NEP support at the moment so please do NOT install NEP in your development folder (and of course no other add-on).

	* Do NOT rename or delete any folder name or CVS will go mad. Do NOT move or copy directories. Be very ~~carefully~~ when you add a directory to the repository because you cannot delete it.		* Do NOT rename or delete any folder name or CVS will go mad. Do NOT move or copy directories. Be very careful when you add a directory to the repository because you cannot delete it.

	* There are lot's of .cvsignore files so CVS should ignore Orbiter files and the VC++ files created during build, we hope everthing works fine but there could be bugs of course.		* There are lot's of .cvsignore files so CVS should ignore Orbiter files and the VC++ files created during build, we hope everthing works fine but there could be bugs of course.

imported>Tschachim: no radiation pressure necessary

2010-09-13T12:47:37Z

no radiation pressure necessary

← Older revision		Revision as of 12:47, 13 September 2010
Line 46:		Line 46:
	* Since there are no modules in the repository first you have to '''compile the sources''' (or install them from the file release). The projects should have a clean debug and release configuration, please try if you can work with them WITHOUT changing them and please report problems to an administrator or at the forum, we'll try to help you as soon as possible.		* Since there are no modules in the repository first you have to '''compile the sources''' (or install them from the file release). The projects should have a clean debug and release configuration, please try if you can work with them WITHOUT changing them and please report problems to an administrator or at the forum, we'll try to help you as soon as possible.

	* Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''', '''Limited fuel~~''', '''Radiation pressure~~''' and '''Gravity-gradient torque''' are enabled. If you're using a Virtual AGC scenario, also enable '''Nonspherical gravity sources'''.		* Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''', '''Limited fuel''' and '''Gravity-gradient torque''' are enabled. If you're using a Virtual AGC scenario, also enable '''Nonspherical gravity sources'''.

	* Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' module.<BR>		* Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' module.<BR>

imported>Tschachim: Orbiter 2010

2010-09-07T15:03:38Z

Orbiter 2010

← Older revision		Revision as of 15:03, 7 September 2010
Line 36:		Line 36:
	* Press "OK". TortoiseCVS downloads now the current version of the Project Apollo files to your computer. Since the download consists of about 240 MB in more than 1.900 files (as of November 2006), this will take some time ...		* Press "OK". TortoiseCVS downloads now the current version of the Project Apollo files to your computer. Since the download consists of about 240 MB in more than 1.900 files (as of November 2006), this will take some time ...

	* After the checkout install Orbiter in your folder, that means in the example above the path of Orbiter is "C:\ProjectApollo\orbiter.exe". This includes the following files at the moment:<BR><BR>'''Orbiter ~~2006~~-P1 Edition''' (http://~~www~~.~~orbitersim~~.~~com~~)		* After the checkout install Orbiter in your folder, that means in the example above the path of Orbiter is "C:\ProjectApollo\orbiter.exe". This includes the following files at the moment:<BR><BR>'''Orbiter 2010-P1 Edition''' (http://orbit.medphys.ucl.ac.uk)
	** ~~orbiter060929_base.zip~~		** orbiter100830.zip<BR><BR>Optional:<BR>
	** orbiter060929_sdk.zip<BR><BR>Optional:<BR>		**Earth091124_11_14.zip
	**~~Earth060504_L10~~.zip		**Moon090730_L11.zip<BR>You can install every other Planetary extension package, too.<BR><BR><div style="margin-left: -1.5em;">'''OrbiterSound 3.5''' (http://orbiter.dansteph.com)</div>
	**~~Moon060504_L8~~.zip<BR>You can install every other Planetary extension package, too.<BR><BR><div style="margin-left: -1.5em;">'''OrbiterSound 3.5''' (http://orbiter.dansteph.com)</div>
	** OrbiterSound35.exe<BR><BR><div style="margin-left: -1.5em;">Orbiter and OrbiterSound should not overwrite any of the CVS files.</div><BR>		** OrbiterSound35.exe<BR><BR><div style="margin-left: -1.5em;">Orbiter and OrbiterSound should not overwrite any of the CVS files.</div><BR>

	* Download and unzip the latest '''Meshland Pack''' using the link at the top of this page in your beta testing folder. Make sure that the "Use Folders" option box is ticked/checked. CVS will ignore the new files. Start Orbiter, go to the "Modules" tab and activate the "MeshLand" module.		* You will find the Project Apollo solution file for '''Microsoft Visual Studio 2005/2008/2010''' in the "ProjectApollo" source folder ("C:\ProjectApollo\Orbitersdk\samples\ProjectApollo\ProjectApollo2005/2008/2010.sln"). All available projects are included in this solution, rebuild all projects to get all necessary modules.

	* You will find the Project Apollo workspace file for '''Microsoft Visual C++ 6.0''' in the "ProjectApollo" source folder ("C:\ProjectApollo\Orbitersdk\samples\ProjectApollo\ProjectApollo.dsw"). All available projects are included in this workspace, rebuild all projects to get all necessary modules.

	* You will find the Project Apollo solution file for '''Microsoft Visual Studio 2005''' in the "ProjectApollo" source folder ("C:\ProjectApollo\Orbitersdk\samples\ProjectApollo\ProjectApollo2005.sln"). All available projects are included in this solution, rebuild all projects to get all necessary modules.

	* Since there are no modules in the repository first you have to '''compile the sources''' (or install them from the file release). The projects should have a clean debug and release configuration, please try if you can work with them WITHOUT changing them and please report problems to an administrator or at the forum, we'll try to help you as soon as possible.		* Since there are no modules in the repository first you have to '''compile the sources''' (or install them from the file release). The projects should have a clean debug and release configuration, please try if you can work with them WITHOUT changing them and please report problems to an administrator or at the forum, we'll try to help you as soon as possible.

	* Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''' ~~and~~ '''Limited fuel''' are enabled. If you're using a Virtual AGC scenario, also enable '''Nonspherical gravity sources'''.		* Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''', '''Limited fuel''', '''Radiation pressure''' and '''Gravity-gradient torque''' are enabled. If you're using a Virtual AGC scenario, also enable '''Nonspherical gravity sources'''.

	* Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' ~~and '''MeshLand''' modules~~.<BR>		* Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' module.<BR>

	* Optionally you can change some options with the '''[[Launchpad_Configuration_Options\|Launchpad Configurator]]''' on the "Extra" tab.<BR>		* Optionally you can change some options with the '''[[Launchpad_Configuration_Options\|Launchpad Configurator]]''' on the "Extra" tab.<BR>

imported>Tschachim: Broken TortoiseCVS warning

2008-06-01T13:34:35Z

Broken TortoiseCVS warning

← Older revision		Revision as of 13:34, 1 June 2008
Line 12:		Line 12:


	{{ Attention \| message=You need a SourceForge login to be able to commit your changes to SourceForge and you have to be added as a developer to Project Apollo by a project administrator. So please make a login for yourself and post an informal request with your login (UNIX name) included that you wants to be added at the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum].}}		{{ Attention \| message=It looks like the latest TortoiseCVS version is '''not working''' with the SourceForge CVS server, so we strongly recommend to use the latest known working version instead, [http://downloads.sourceforge.net/tortoisecvs/TortoiseCVS-1.8.29.exe TortoiseCVS 1.8.29].


			You need a SourceForge login to be able to commit your changes to SourceForge and you have to be added as a developer to Project Apollo by a project administrator. So please make a login for yourself and post an informal request with your login (UNIX name) included that you wants to be added at the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum].}}

imported>Tschachim: OrbiterSound 3.5

2007-06-06T15:13:45Z

OrbiterSound 3.5

← Older revision		Revision as of 15:13, 6 June 2007
Line 37:		Line 37:
	** orbiter060929_sdk.zip<BR><BR>Optional:<BR>		** orbiter060929_sdk.zip<BR><BR>Optional:<BR>
	**Earth060504_L10.zip		**Earth060504_L10.zip
	**Moon060504_L8.zip<BR>You can install every other Planetary extension package, too.<BR><BR><div style="margin-left: -1.5em;">'''OrbiterSound 3.0''' (http://orbiter.dansteph.com)</div>		**Moon060504_L8.zip<BR>You can install every other Planetary extension package, too.<BR><BR><div style="margin-left: -1.5em;">'''OrbiterSound 3.5''' (http://orbiter.dansteph.com)</div>
	** ~~OrbiterSound30~~.exe<BR><BR><div style="margin-left: -1.5em;">Orbiter and OrbiterSound should not overwrite any of the CVS files.</div><BR>		** OrbiterSound35.exe<BR><BR><div style="margin-left: -1.5em;">Orbiter and OrbiterSound should not overwrite any of the CVS files.</div><BR>

	* Download and unzip the latest '''Meshland Pack''' using the link at the top of this page in your beta testing folder. Make sure that the "Use Folders" option box is ticked/checked. CVS will ignore the new files. Start Orbiter, go to the "Modules" tab and activate the "MeshLand" module.		* Download and unzip the latest '''Meshland Pack''' using the link at the top of this page in your beta testing folder. Make sure that the "Use Folders" option box is ticked/checked. CVS will ignore the new files. Start Orbiter, go to the "Modules" tab and activate the "MeshLand" module.

imported>Tschachim: Add/remove files

2007-03-15T19:01:52Z

Add/remove files

← Older revision		Revision as of 19:01, 15 March 2007
Line 10:		Line 10:

	We recommend '''[http://www.tortoisecvs.org TortoiseCVS]''' as client, so first of all please download and install it. You will also find some instructions especially for SourceForge in the TortoiseCVS help. We also recommend to take the time to read the "Using TortoiseCVS with SourceForge" chapter and the "Using Pageant to avoid having to enter the SSH password every time" chapter in the help file and to use Pageant.		We recommend '''[http://www.tortoisecvs.org TortoiseCVS]''' as client, so first of all please download and install it. You will also find some instructions especially for SourceForge in the TortoiseCVS help. We also recommend to take the time to read the "Using TortoiseCVS with SourceForge" chapter and the "Using Pageant to avoid having to enter the SSH password every time" chapter in the help file and to use Pageant.


	{{ Attention \| message=You need a SourceForge login to be able to commit your changes to SourceForge and you have to be added as a developer to Project Apollo by a project administrator. So please make a login for yourself and post an informal request with your login (UNIX name) included that you wants to be added at the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum].}}		{{ Attention \| message=You need a SourceForge login to be able to commit your changes to SourceForge and you have to be added as a developer to Project Apollo by a project administrator. So please make a login for yourself and post an informal request with your login (UNIX name) included that you wants to be added at the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum].}}


	If you use CVS the first time you can practice the basic CVS operations with the test module (named "test"). Do the checkout as explained below, but use "test" as module. You'll get some test files you can change as you like to get familiar with CVS.		If you use CVS the first time you can practice the basic CVS operations with the test module (named "test"). Do the checkout as explained below, but use "test" as module. You'll get some test files you can change as you like to get familiar with CVS.
Line 53:		Line 55:

	* That all, now you can try if Orbiter and Project Apollo is working. You'll find the proper scenarios in the '''"Project Apollo - NASSP" scenario folder''' and subfolders.		* That all, now you can try if Orbiter and Project Apollo is working. You'll find the proper scenarios in the '''"Project Apollo - NASSP" scenario folder''' and subfolders.

			== Update your local files ==

			To get the changes of the other users you don't have to do the checkout again (in fact you must not) but you have to use the '''"CVS Update"''' feature:

			Choose the "CVS Update" menu item from the Tortoise context menu for each folder below "C:\ProjectApollo", i.e. "Config", "Doc", "Html" etc. CVS will download the changed files and merge the changes into your local copies.

			If you receive an update of a file you are editing at the moment it can happen that merging is not possible and you get a "confict". If you have problems resolving the confict please contact a project administrator for assistants, this is always a difficult situation.

	== Edit a file ==		== Edit a file ==
Line 60:		Line 70:
	Alternatively you can just overwrite the read-only file, but then CVS won't be able to tell other users that you're editing the same file as they are.		Alternatively you can just overwrite the read-only file, but then CVS won't be able to tell other users that you're editing the same file as they are.

	== ~~Commit your changes~~ ==		== Add a file ==

	~~When you finished changing~~ a file ~~you can commit it (~~save it~~) to~~ the CVS ~~repository by choosing~~ the '''"CVS ~~Commit~~..."~~'''~~ context menu ~~item. Please provide a useful comment~~ in the ~~commit window. If the committed file is a source file, your comment will be added to the revision history at the top of the file~~.		To add a file just save it at the appropriate location at first. CVS doesn't know it yet and so it is marked with a small question mark icon. To add the file you have to do a '''"CVS Add"''' with the file (by choosing "CVS Add..." in the Tortoise context menu and then pressing "OK" in the next dialog).

	~~If you don't want to commit your changes (and undo it) please choose "CVS Unedit" instead.~~		== Delete a file ==

	~~== Update your~~ local ~~files ==~~		To add the file you have to do a '''"CVS Remove"''' with the file (by choosing "Remove" in the Tortoise context menu). The local file is removed (moved to the Windows Recyle Bin), but the change isn't committed yet. You need to do a '''"CVS Commit"''' with ''the directory, which contained the file (right-click on the folder to get the CVS context menu)'', to remove it from the CVS server (which has a "Recyle Bin", too, so nothing gets lost).

	~~To get the~~ changes ~~of the other users you don't have to do the checkout again (in fact you must not) but you have to use the '''"CVS Update"''' feature:~~		== Commit your changes ==

	~~Choose~~ the "CVS ~~Update~~" menu item ~~from the Tortoise context menu for each folder below~~ "~~C:\ProjectApollo~~"~~, i~~.e. ~~"Config"~~, ~~"Doc", "Html" etc. CVS~~ will ~~download~~ the ~~changed~~ files ~~and merge the changes into your local copies~~.		When you finished changing one or many files you can commit them (upload and save them) to the CVS repository by choosing the '''"CVS Commit..."''' context menu item. Also you can choose "CVS Commit..." for a directory (and need to in case of removed files) to commit all changes in this directory and all subdirectories. Please provide a useful comment in the commit window. If the committed files are source code files, your comment will be added to the revision history at the top of the files.

	If you ~~receive an update of a file you are editing at the moment~~ it ~~can happen that merging is not possible and you get a~~ "~~confict~~"~~. If you have problems resolving the confict please contact a project administrator for assistants, this is always a difficult situation~~.		If you don't want to commit your changes (and undo it) please choose "CVS Unedit" instead.

	== Comments and remarks ==		== Comments and remarks ==
Line 78:		Line 88:
	* There is no NEP support at the moment so please do NOT install NEP in your development folder (and of course no other add-on).		* There is no NEP support at the moment so please do NOT install NEP in your development folder (and of course no other add-on).

	* Do NOT rename or delete any folder name or CVS will go mad. Be very carefully when you add a directory to the repository because you cannot delete it.		* Do NOT rename or delete any folder name or CVS will go mad. Do NOT move or copy directories. Be very carefully when you add a directory to the repository because you cannot delete it.

	* There are lot's of .cvsignore files so CVS should ignore Orbiter files and the VC++ files created during build, I hope everthing works fine but there could be bugs of course.		* There are lot's of .cvsignore files so CVS should ignore Orbiter files and the VC++ files created during build, we hope everthing works fine but there could be bugs of course.

	* If you have problems or need help please mail to an administrator, an other developer or post in the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum] and we will help you to solve your problem.		* If you have problems or need help please mail to an administrator, an other developer or post in the [http://www.ibiblio.org/mscorbit/mscforum Project Apollo forum] and we will help you to solve your problem.

imported>Tschachim: /* Initial Checkout */ MFD link

2006-12-19T17:54:15Z

Initial Checkout: MFD link

← Older revision		Revision as of 17:54, 19 December 2006
Line 48:		Line 48:
	* Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''' and '''Limited fuel''' are enabled. If you're using a Virtual AGC scenario, also enable '''Nonspherical gravity sources'''.		* Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''' and '''Limited fuel''' are enabled. If you're using a Virtual AGC scenario, also enable '''Nonspherical gravity sources'''.

	* Go to the "Modules" tab and activate the '''ProjectApolloMFD''' and '''MeshLand''' modules.<BR>		* Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' and '''MeshLand''' modules.<BR>

	* Optionally you can change some options with the '''[[Launchpad_Configuration_Options\|Launchpad Configurator]]''' on the "Extra" tab.<BR>		* Optionally you can change some options with the '''[[Launchpad_Configuration_Options\|Launchpad Configurator]]''' on the "Extra" tab.<BR>

imported>Tschachim: Added launchpad configurator link.

2006-11-13T16:32:25Z

Added launchpad configurator link.

← Older revision		Revision as of 16:32, 13 November 2006
Line 49:		Line 49:

	* Go to the "Modules" tab and activate the '''ProjectApolloMFD''' and '''MeshLand''' modules.<BR>		* Go to the "Modules" tab and activate the '''ProjectApolloMFD''' and '''MeshLand''' modules.<BR>

			* Optionally you can change some options with the '''[[Launchpad_Configuration_Options\|Launchpad Configurator]]''' on the "Extra" tab.<BR>

	* That all, now you can try if Orbiter and Project Apollo is working. You'll find the proper scenarios in the '''"Project Apollo - NASSP" scenario folder''' and subfolders.		* That all, now you can try if Orbiter and Project Apollo is working. You'll find the proper scenarios in the '''"Project Apollo - NASSP" scenario folder''' and subfolders.