Re: Splitting Validate_* packages into separate git repositories

On 2013-03-24 20:13, Daniel O'Connor wrote:

Here's roughly process I was following: Fork the Validate repo Rename the fork to Validate_XY $ cd Validate_XY $ git mv package_XY.xml package.xml $ git rm package_*.xml $ pear list package.xml # git rm anything not listed there, in test/*, data/*, etc $ git commit -m "Splitting" $ cd Validate $ rm package_XY.xml $ rm test/test_XY.phpt $ rm data/XY.csv ... etc $ git commit -m "Splitting" $ git push Make a new repo in the PEAR organisation $ cd ../Validate_XY $ git remote add new_repo git@github.com:pear/Validate_XY.git $ git push new_repo master Unfortunately, its a bit time consuming to do all of this vs the number of subpackages - feel free to take up where I've left off!

Thanks, I've split all remaining Validate_* packages into their own repositories: * https://github.com/pear/Validate_esMX * https://github.com/pear/Validate_LV * https://github.com/pear/Validate_NZ * https://github.com/pear/Validate_IT * https://github.com/pear/Validate_IR * https://github.com/pear/Validate_IE * https://github.com/pear/Validate_FI * https://github.com/pear/Validate_UK * https://github.com/pear/Validate_Finance_CreditCard Validate_FR had a package_FR.xml in the Validate repo but was previously split into its own repo. I removed the package_FR.xml from the Validate repo. Each new repo has the pear/validate-team-collective team added. Each package on pear.php.net was updated to point to the new repos (except for esMX which doesn't have a package). My mind is now pretty numb so I may have messed up somewhere. Email the list if you notice anything odd, or if you are a validate maintainer who is not part of the validate-team-collective. Cheers, Mike