PLDWWW: Docs/CVSMigration

[mmazur]

Author: mmazur   Date: Fri Apr  3 22:39:23 2009 GMT
Module: PLDWWW   URL: http://pld-linux.org/Docs/CVSMigration?action=diff&rev2=2&rev1=1
---- Log message:
formatting

---- Page affected: Docs/CVSMigration

---- Diffs:

================================================================
The comment on the change is:
formatting

  Note: certainly not to SVN (it's old), most likely either git or mercurial.
  
  
- 1. A script that will assign all files in SOURCES to their relevant spec files (in SPECS) and list both orphans and duplicates.
+  1. A script that will assign all files in SOURCES to their relevant spec files (in SPECS) and list both orphans and duplicates.
  
- 2. A script that will do the actual CVS->somethingelse translation while preserving history of both sources and spec files.
+  2. A script that will do the actual CVS->somethingelse translation while preserving history of both sources and spec files.
  
- 3. 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.
+  3. 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.
  
- 4. pld-builder.new (well, the SPECS/builder script actually) needs to support the new way of fetching packages and tagging.
+  4. pld-builder.new (well, the SPECS/builder script actually) needs to support the new way of fetching packages and tagging.
  
- 5. Server-side rules needs to be enforce: auto-th tags can't be developer-assignable.
+  5. Server-side rules needs to be enforce: auto-th tags can't be developer-assignable.
  
- 6. New package repository creation (and maybe renaming) must be easy.
+  6. New package repository creation (and maybe renaming) must be easy.