This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
docs:cvsmigration [2009-04-04 00:38] mmazur |
docs:cvsmigration [2009-04-20 16:04] mmazur |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | 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. | ||
- | |||
- | 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. | ||
- | |||
- | 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. | ||
- | |||
- | 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. | ||
- | |||