Elphel on SourceForge - Revision history

Andrey.filippov at 23:36, 17 March 2020

2020-03-17T23:36:19Z

← Older revision		Revision as of 23:36, 17 March 2020
Line 1:		Line 1:
			{{Legacy}}
			'''Elphel currently uses git repository at https://git.elphel.com, mirrored at https://github.com/Elphel'''


	= Releases description on Elphel's SourceForge project=		= Releases description on Elphel's SourceForge project=

OneArtPlease: /* '''Add files or directories to the repository:''' */

2009-07-29T07:59:14Z

'''Add files or directories to the repository:'''

← Older revision		Revision as of 07:59, 29 July 2009
Line 113:		Line 113:

	=='''Add files or directories to the repository:'''==		=='''Add files or directories to the repository:'''==
	* 1 - add the new files to the CVS, remove old ones that are not replaced, if any (don't need to commit changes yet, but if you do - update first)
	* 2 - edit src.list to add those new files, comment out the old unneeded ones with '#', files in the same level should go in alphabetical order. Run ./diff_srclist_cvs script in the top directory, make sure it comes out with empty output		See the [[CVS_commit \| CVS commit checklist]].
	* 3 - modify Makefile in your installation directory so it will install the new files (and do not install old ones if you removed them!)
	* 4 - in the case you added the new subdirectory with it's own Makefile that needs to run during build - edit subdirs.list and add you directory. Usually the new directories are added the very end (if none other depend on them)
	* 5 - currently there is no automatic way to verify that Makefile will not try to use non-existent (in src.list, CVS) files, so it would be nice if you run top make now, generate source archive and install it in the new directory, making sure 'make' is happy and was able to find everything it needed. If you got any problems at this stage and do not have immediate solution - just remove this directory from the subdirs.list until the issue is resolved. If you do this and if the ./diff_srclist_cvs output is empty - it is safe to commit changes to the CVS without breaking installation.
	* 6 - update from the CVS ~~first before making any commits. You can use "make update" command from the top directory~~
	* 7 - commit ~~all the changes made to the CVS (add/remove files, modified src~~.~~list, Makefile(s)), provide descriptive commit messag~~

Andrey.filippov: /* Setting up developer CVS access to elphel/elphel-community projects at Sourceforge */

2009-01-23T19:32:13Z

Setting up developer CVS access to elphel/elphel-community projects at Sourceforge

Andrey.filippov at 19:28, 23 January 2009

2009-01-23T19:28:16Z

← Older revision		Revision as of 19:28, 23 January 2009
Line 28:		Line 28:
	After you install the Elphel software using ./install_elphel (either from the source archive or the CVS, manually or using the script) you may get to the top working directory ( by default it is called "elphel353" and has subdirectories starting with "apps") and run		After you install the Elphel software using ./install_elphel (either from the source archive or the CVS, manually or using the script) you may get to the top working directory ( by default it is called "elphel353" and has subdirectories starting with "apps") and run
	make update		make update
	If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you'll be able to upgrade it as described [[Elphel_on_SourceForge#Setting_up_developer_CVS_access_to_elphel.2Felphel-community_projects_at_Sourceforge\|below]]		If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you'll be able to upgrade it as described [[Elphel_on_SourceForge#Setting_up_developer_CVS_access_to_elphel.2Felphel-community_projects_at_Sourceforge\|below]]. After "make update" you may just open the elphel353 directory in the Cervisia and enjoy using CVS without the need to remember the command line options fro the cvs command. The only configuration setting you'll likely want to change is "update recursively" checkbox in the "Settings". Then if you right-click the top elphel353 directory and select "update" it will update all the project files, not just the ones in that top directory.

	= Setting up developer CVS access to elphel/elphel-community projects at Sourceforge =		= Setting up developer CVS access to elphel/elphel-community projects at Sourceforge =

Andrey.filippov: /* Elhel CVS and Cervisia (GUI front end to the CVS) */

2009-01-23T19:23:53Z

Elhel CVS and Cervisia (GUI front end to the CVS)

← Older revision		Revision as of 19:23, 23 January 2009
Line 28:		Line 28:
	After you install the Elphel software using ./install_elphel (either from the source archive or the CVS, manually or using the script) you may get to the top working directory ( by default it is called "elphel353" and has subdirectories starting with "apps") and run		After you install the Elphel software using ./install_elphel (either from the source archive or the CVS, manually or using the script) you may get to the top working directory ( by default it is called "elphel353" and has subdirectories starting with "apps") and run
	make update		make update
	If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you'll be able to upgrade it as described [[Elphel_on_SourceForge#Setting_up_developer_CVS_access_to_elphel.2Felphel-community_projects_at_Sourceforge below]]		If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you'll be able to upgrade it as described [[Elphel_on_SourceForge#Setting_up_developer_CVS_access_to_elphel.2Felphel-community_projects_at_Sourceforge\|below]]

	= Setting up developer CVS access to elphel/elphel-community projects at Sourceforge =		= Setting up developer CVS access to elphel/elphel-community projects at Sourceforge =

Andrey.filippov at 19:23, 23 January 2009

2009-01-23T19:23:09Z

← Older revision		Revision as of 19:23, 23 January 2009
Line 28:		Line 28:
	After you install the Elphel software using ./install_elphel (either from the source archive or the CVS, manually or using the script) you may get to the top working directory ( by default it is called "elphel353" and has subdirectories starting with "apps") and run		After you install the Elphel software using ./install_elphel (either from the source archive or the CVS, manually or using the script) you may get to the top working directory ( by default it is called "elphel353" and has subdirectories starting with "apps") and run
	make update		make update
	If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you ~~need~~ to ~~do the following:~~		If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you'll be able to upgrade it as described [[Elphel_on_SourceForge#Setting_up_developer_CVS_access_to_elphel.2Felphel-community_projects_at_Sourceforge below]]

	= Setting up developer CVS access to elphel/elphel-community projects at Sourceforge =		= Setting up developer CVS access to elphel/elphel-community projects at Sourceforge =

Andrey.filippov at 19:19, 23 January 2009

2009-01-23T19:19:21Z

← Older revision		Revision as of 19:19, 23 January 2009
Line 29:		Line 29:
	make update		make update
	If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you need to do the following:		If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you need to do the following:

			= Setting up developer CVS access to elphel/elphel-community projects at Sourceforge =
	* Get developer status from one of the project admins (elphel or elphel-community), ''your_sf_username'' below is your Sourceforge user name		* Get developer status from one of the project admins (elphel or elphel-community), ''your_sf_username'' below is your Sourceforge user name
	* Create SSH key for you computer (with empty pass phrase ) and post it at sourceforge (posting is on you personal page, not on the project page)		* Create SSH key for you computer (with empty pass phrase ) and post it at sourceforge (posting is on you personal page, not on the project page)
Line 43:		Line 45:
	Number of SSH Shared Keys on file: 0 [Edit SSH Keys for Shell/CVS]		Number of SSH Shared Keys on file: 0 [Edit SSH Keys for Shell/CVS]

	And then open [https://sourceforge.net/account/editsshkeys.php Edit SSH Keys for Shell/CVS] link (that direct link here should also work if you are already logged in to [https://sourceforge.net] )		And then open [https://sourceforge.net/account/editsshkeys.php Edit SSH Keys for Shell/CVS] link (that direct link here should also work if you are already logged in to [https://sourceforge.net Sourceforge] )
	Then just paste the "ssh-dss ... @elphel.cvs.sourceforge.net" line into the form (it will end with elphelcommunity.cvs.sourceforge.net if you are working with "elphel-community", not "elphel" repository)		Then just paste the "ssh-dss ... @elphel.cvs.sourceforge.net" line into the form (it will end with elphelcommunity.cvs.sourceforge.net if you are working with "elphel-community", not "elphel" repository)

Line 56:		Line 58:
	You cannot execute anything here.		You cannot execute anything here.
	Connection to elphel.cvs.sourceforge.net closed.		Connection to elphel.cvs.sourceforge.net closed.
			Sourceforge states that there could be delay between posting a key and it becoming active, but it always worked for me immediately. If you do not see "Welcome to *.cvs.sourceforge.net" - try it later or recheck steps above and your CVS permissions in elphel/elphel-community projects.

			If you got that "Welcome..." you are now ready to update CVS information (in those 'CVS' directories) to use developer access. First - remove the 'CVS' directory from the top directory of the project ('elphel353/CVS' by default), you do not need to remove CVS in subdirectories. Then re-run
			make update
			And use your_sf_username when prompted (no password will be asked, security will rely on that key generated and posted above)

			All done, now you can use CVS (and Cervisia) with commit, in Cervisia it is right-click on the file(s) and select "commit" in the context menu.

Andrey.filippov at 19:09, 23 January 2009

2009-01-23T19:09:13Z

← Older revision		Revision as of 19:09, 23 January 2009
Line 22:		Line 22:

	== Under development tree ==		== Under development tree ==
			= Elhel CVS and Cervisia (GUI front end to the CVS) =
			'''TODO:''' Not all of the functionality described below applies to the elphel-community project, that should be done
			It is possible to use Cervisia (unfortunately Konqueror integration as of now is broken in KDE 4.X, so it should be run as a standalone program).
			<!-- - there are scripts for the elphel project (official) that do it for both 7.1.x and 8.0.x branches. -->
			After you install the Elphel software using ./install_elphel (either from the source archive or the CVS, manually or using the script) you may get to the top working directory ( by default it is called "elphel353" and has subdirectories starting with "apps") and run
			make update
			If you run it for the first time it will create CVS-related directories and files (all directories are called 'CVS'). If you did that for anonymous user (read only access) and later want to upgrade to developer (read/write) access you need to do the following:
			* Get developer status from one of the project admins (elphel or elphel-community), ''your_sf_username'' below is your Sourceforge user name
			* Create SSH key for you computer (with empty pass phrase ) and post it at sourceforge (posting is on you personal page, not on the project page)
			ssh-keygen -t dsa -C " your_sf_username@elphel.cvs.sourceforge.net"
			or
			ssh-keygen -t dsa -C " your_sf_username@elphelcommunity.cvs.sourceforge.net"
			Agree with defaults, use empty passphrase
			You will get
			Your public key has been saved in (your home directory)/.ssh/id_dsa.pub.
			Copy the long line related to this host, something like
			ssh-dss AAAAB... (clipped) ...Gvs your_sf_username@elphel.cvs.sourceforge.net
			to the copy buffer.
			Login to Sourceforge, go to your account (link "Account" on the top-right in the browser page) and scroll down until you find (number of keys may be different)
			Number of SSH Shared Keys on file: 0 [Edit SSH Keys for Shell/CVS]

			And then open [https://sourceforge.net/account/editsshkeys.php Edit SSH Keys for Shell/CVS] link (that direct link here should also work if you are already logged in to [https://sourceforge.net] )
			Then just paste the "ssh-dss ... @elphel.cvs.sourceforge.net" line into the form (it will end with elphelcommunity.cvs.sourceforge.net if you are working with "elphel-community", not "elphel" repository)

			Next step - you need to connect manually to the repository using ssh:
			ssh your_sf_username@elphel.cvs.sourceforge.net
			or
			ssh your_sf_username@elphelcommunity.cvs.sourceforge.net

			The server will throw you away, but before that you'll agree to connect to that server so the system will not try to ask the scripts or Cervisia about it later.
			Welcome to *.cvs.sourceforge.net
			This is a restricted Shell Account
			You cannot execute anything here.
			Connection to elphel.cvs.sourceforge.net closed.








	= How to contribute to Elphel CVS =		= How to contribute to Elphel CVS =

Andrey.filippov: /* How to contribute to Elphel CVS */

2009-01-23T18:30:41Z

How to contribute to Elphel CVS

← Older revision		Revision as of 18:30, 23 January 2009
Line 30:		Line 30:


	The goal is to overcome the need to ~~froze~~ the official Elphel CVS at some times		The goal is to overcome the need to freeze the official Elphel CVS at some times

	(to issue stable releases), without having to resolve unexpected third~~-parties~~ import		(to issue stable releases), without having to resolve unexpected third party import

	related conflicts first.		related conflicts first.
Line 42:		Line 42:

	possible, after validation.		possible, after validation.




Line 65:		Line 67:

	cd elphel353-7.1-community && cvs -z3 -d:pserver:anonymous@elphelcommunity.cvs.sourceforge.net:/cvsroot/elphelcommunity udpate		cd elphel353-7.1-community && cvs -z3 -d:pserver:anonymous@elphelcommunity.cvs.sourceforge.net:/cvsroot/elphelcommunity udpate



	=='''Add files or directories to the repository:'''==		=='''Add files or directories to the repository:'''==
			* 1 - add the new files to the CVS, remove old ones that are not replaced, if any (don't need to commit changes yet, but if you do - update first)
			* 2 - edit src.list to add those new files, comment out the old unneeded ones with '#', files in the same level should go in alphabetical order. Run ./diff_srclist_cvs script in the top directory, make sure it comes out with empty output
			* 3 - modify Makefile in your installation directory so it will install the new files (and do not install old ones if you removed them!)
			* 4 - in the case you added the new subdirectory with it's own Makefile that needs to run during build - edit subdirs.list and add you directory. Usually the new directories are added the very end (if none other depend on them)
			* 5 - currently there is no automatic way to verify that Makefile will not try to use non-existent (in src.list, CVS) files, so it would be nice if you run top make now, generate source archive and install it in the new directory, making sure 'make' is happy and was able to find everything it needed. If you got any problems at this stage and do not have immediate solution - just remove this directory from the subdirs.list until the issue is resolved. If you do this and if the ./diff_srclist_cvs output is empty - it is safe to commit changes to the CVS without breaking installation.
			* 6 - update from the CVS first before making any commits. You can use "make update" command from the top directory
			* 7 - commit all the changes made to the CVS (add/remove files, modified src.list, Makefile(s)), provide descriptive commit messag


	* 1 - commit to the CVS new files
	* 2 - edit src.list accordingly, so when you run ./diff_srclist_cvs in the top directory it comes with empty outpu
	* 3 - modify Makefile in your installation directory so it will install the new files (and do not install old ones if you removed them)

	cd elphel353-7.1-community && cvs -z3 -d:ext:USER@elphelcommunity.cvs.sourceforge.net:/cvsroot/elphelcommunity add <file> -m "description"		cd elphel353-7.1-community && cvs -z3 -d:ext:USER@elphelcommunity.cvs.sourceforge.net:/cvsroot/elphelcommunity add <file> -m "description"
Line 98:		Line 106:


	'''Technical details (for Elphel ~~staff~~) about repository setup and update:'''		'''Technical details (for Elphel stuff) about repository setup and update:'''

Polto: /* How to contribute to Elphel CVS */

2009-01-23T10:50:24Z

How to contribute to Elphel CVS

← Older revision		Revision as of 10:50, 23 January 2009
Line 67:		Line 67:


	'''Add files or directories to the repository:''' (you ~~need to commit changes with "cvs commit <file>"~~)		=='''Add files or directories to the repository:'''==

			* 1 - commit to the CVS new files
			* 2 - edit src.list accordingly, so when you run ./diff_srclist_cvs in the top directory it comes with empty outpu
			* 3 - modify Makefile in your installation directory so it will install the new files (and do not install old ones if you removed them)

	cd elphel353-7.1-community && cvs -z3 -d:ext:USER@elphelcommunity.cvs.sourceforge.net:/cvsroot/elphelcommunity add <file> -m "description"		cd elphel353-7.1-community && cvs -z3 -d:ext:USER@elphelcommunity.cvs.sourceforge.net:/cvsroot/elphelcommunity add <file> -m "description"

← Older revision		Revision as of 19:32, 23 January 2009
Line 45:		Line 45:
	Number of SSH Shared Keys on file: 0 [Edit SSH Keys for Shell/CVS]		Number of SSH Shared Keys on file: 0 [Edit SSH Keys for Shell/CVS]

	And then open [https://sourceforge.net/account/editsshkeys.php Edit SSH Keys for Shell/CVS] link (that direct link here should also work if you are already logged in to [https://sourceforge.net Sourceforge] )		* And then open [https://sourceforge.net/account/editsshkeys.php Edit SSH Keys for Shell/CVS] link (that direct link here should also work if you are already logged in to [https://sourceforge.net Sourceforge] ). Paste the "ssh-dss ... @elphel.cvs.sourceforge.net" line into the form (it will end with elphelcommunity.cvs.sourceforge.net if you are working with "elphel-community", not "elphel" repository), submit the changes.
	~~Then just paste~~ the "ssh-dss ... @elphel.cvs.sourceforge.net" line into the form (it will end with elphelcommunity.cvs.sourceforge.net if you are working with "elphel-community", not "elphel" repository)

	Next step - you need to connect manually to the repository using ssh:		* Next step - you need to connect manually to the repository using ssh:
	ssh your_sf_username@elphel.cvs.sourceforge.net		ssh your_sf_username@elphel.cvs.sourceforge.net
	or		or
	ssh your_sf_username@elphelcommunity.cvs.sourceforge.net		ssh your_sf_username@elphelcommunity.cvs.sourceforge.net

	The server will throw you away, but before that you'll agree to connect to that server so the system will not try to ask the scripts or Cervisia about it later.		The server will throw you away, but before that you'll agree to connect to that server so the system (your computer, not the Sourceforge) will not try to ask the scripts or Cervisia about it later.
	Welcome to *.cvs.sourceforge.net		Welcome to *.cvs.sourceforge.net
	This is a restricted Shell Account		This is a restricted Shell Account
Line 60:		Line 59:
	Sourceforge states that there could be delay between posting a key and it becoming active, but it always worked for me immediately. If you do not see "Welcome to *.cvs.sourceforge.net" - try it later or recheck steps above and your CVS permissions in elphel/elphel-community projects.		Sourceforge states that there could be delay between posting a key and it becoming active, but it always worked for me immediately. If you do not see "Welcome to *.cvs.sourceforge.net" - try it later or recheck steps above and your CVS permissions in elphel/elphel-community projects.

	If you got that "Welcome..." you are now ready to update CVS information (in those 'CVS' directories) to use developer access. First - remove the 'CVS' directory from the top directory of the project ('elphel353/CVS' by default), you do not need to remove CVS in subdirectories. Then re-run		* If you got that "Welcome..." you are now ready to update CVS information (in those 'CVS' directories) to use developer access. First - remove the 'CVS' directory from the top directory of the project ('elphel353/CVS' by default), you do not need to remove CVS in subdirectories. Then re-run
	make update		make update
	And use your_sf_username when prompted (no password will be asked, security will rely on that key generated and posted above)		And use your_sf_username when prompted (no password will be asked, security will rely on that key generated and posted above)

	All done, now you can use CVS (and Cervisia) with commit, in Cervisia it is right-click on the file(s) and select "commit" in the context menu.		* All done, now you can use CVS (and Cervisia) with commit, in Cervisia it is right-click on the file(s) and select "commit" in the context menu.


	= How to contribute to Elphel CVS =		= How to contribute to Elphel CVS =