I thought that the import command together with the vendor branch was able to cope with this problem (i.e.: just do 'cvs import your_repository THIRD_PARTY_BRANCH a_new_release_tag' should be fine). Isn't?
Cyrille >Hi everybody, > >I'm tracking a third party software within my CVS repository. Till now, what >I've done is this: >1.- Downloaded the initial release of the 3rd party software. >2.- Create a new module within my CVS repository. >3.- Work within the HEAD main branch. > >Now, another release of that 3rd party software has been published, and I >would like to update my CVS repository. The first problem that I've come up >with, is this one: there is no patch-like incremental release. > >To deal with this, I have tried to follow these steps: >1.- Download that new realese. >2.- Export the old release of that package from my CVS repository: > $ cvs export -r THIRD_PARTY_BRANCH package >3.- Create a patch file with diff, with the changes from the old to the new >release of the package: > $ diff -rP <old version dir> <new version dir> > patch.file >4.- Checkout the branch fro the 3rd party tracking: > $ cvs checkout -r THIRD_PARTY package >5.- Apply the patch file to the module: > $ cd package > $ patch -Np1 patch.file >6.- Commit changes. > >But in step 5, it tells me that it cannot find the files to patch... what am >I doing wrong? > >Thank you all in advance, and best regards > >Miguel �ngel Ripalda Mar�n -------------------------------------- Cyrille Bollu - Software Development Engineer AWTCE - Navigation Department Tel. +32 2 389 25 14 Fax. +32 2 389 12 13 mailto:[EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
