User Tools

Site Tools


docs:cvsmigration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
docs:cvsmigration [2009-04-05 18:42]
mmazur
docs:cvsmigration [2009-04-20 16:04]
mmazur
Line 1: Line 1:
- 
- 
-===== Intro ===== 
-Work in progress. Problems that need to get solved before migrating packages from CVS (and into a one-repo-per-spec configuration) is possible. ​ 
- 
-Note: certainly not to SVN (it's old), most likely either git or mercurial. ​ 
- 
- 
- 
-===== Todo ===== 
- 
-  - A script that will assign all files in SOURCES to their relevant spec files (in SPECS) and list both orphans and duplicates. ​ 
-Mostly done. Look at [[http://​ep09.pld-linux.org/​~mmazur/​pld/​specssources.data/​|http://​ep09.pld-linux.org/​~mmazur/​pld/​specssources.data/​]] (and hg clone [[http://​ep09.pld-linux.org/​~mmazur/​pld/​specssources/​|http://​ep09.pld-linux.org/​~mmazur/​pld/​specssources/​]]). ​ 
- 
- 
-  - A script that will do the actual CVS->​somethingelse translation while preserving history of both sources and spec files. ​ 
-  - Some kind of configuration that will make it possible in a reasonably comfortable manner to do mass commits on SPECS, since they'​re a fact of life and quite useful. ​ 
-  - pld-builder.new (well, the SPECS/​builder script actually) needs to support the new way of fetching packages and tagging. ​ 
-  - Server-side rules needs to be enforce: auto-th tags can't be developer-assignable. ​ 
-  - New package repository creation (and maybe renaming) must be easy.  
- 
- 
-===== Problematic spec files ===== 
-No revision 1.1: hlds.spec gkaraoke.spec webcleaner.spec wmusic.spec ​ 
- 
  
docs/cvsmigration.txt · Last modified: 2009-04-20 16:04 by mmazur