Source control / implementation management of an existing open source project

I am currently installing and setting up an open source project on a test server. I was well prepared to use source control, and I want to make sure that everything I do is managed properly (both for me, for the sole developer / administrator, and for future managers). An open source project is available as a source download or through svn checkout.

I want to have my own version of a project with a controlled version. I don’t intend to change the code much (Java servlet) (at least for all), but there are configurations, XML, XSL, CSS files, etc. All this is due to the fact that I definitely want to be a controlled source.

Should I go further and just create my own local repository of all the source code? Should I try to control the files I need to change? In this case, I would like the directory structure to match, so I could do the checks directly in the assembly directories.

+3
source share
3 answers

Having two checks in the same directory tree will not work. If you check your source and try to check the source of the OSS project, any directory with which they have in common will fail, saying that it is already the working directory for another project.

css, xml, xsl .. , svn, OSS.

~/Working = > svn://samhoice/project/trunk

~//osscomponent = > svn://osshost/project/latesttag

~/working/osscomponent/config = > svn://samhoice/project/trunk/config

osscomponent samhoice svn. script OSS. OSS . script, .

, . , svn- .

, OSS, makefile config script. , svn-.

​​ , . , .

+1

, , , , - . , ..

SVN :

branches/
tags/
trunk/

( ) , , , . .. , . , .

- . , , foo-dist, . , foo-dist foo, .

Google, Sourceforge github , ? , - , ..

+1

:

  • . , . " ", , .

  • . ( .tar.bz2 .zip) . , .

    • () . , .

    • script, . , script , ( ) ( ). , , .

  • , " ", " , - . " " . . , - , , , . .

I cannot emphasize that it is necessary to document the entire process of creating such a project and adding settings, or to automate it or (preferably) both. . It is surprisingly easy to forget which files belong to where, or to whom, and it hurts to start over. Especially if you are the heir.

Good luck

+1
source

Source: https://habr.com/ru/post/1698917/


All Articles