-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Lapo Luchini wrote:
> What is your (and/or the suggested) way to "upgrade" a package to next
> release? Do you have a script for that too?
> (with g-b-s I usually ended up using SED on the .patch to change
> directory names and try to apply it on the new sources directly,
> adjusting thing when needs be, and I guess I could do something similar
> using cygport too, at the worst)
With cygport, you don't need to sed the patch, because cygport does 'cd
${S}' before attempting to apply the patch and adjusts the -p flag
accordingly, ignoring the versioned top-level directory.
In short, in the most common case that the patch will apply in the newer
version, I just do (with the help of bash-completion), e.g.:
rename 3 4 foo-0.9.3-1.*
cygport foo-0.9.4-1 get prep
[hopefully patch applies, otherwise fix and apply manually...]
cygport foo-0.9.4-1 build install pkg
cp foo-0.9.4-1/patch/foo-0.9.4-1.src.patch .
cp -r foo-0.9.4-1/dist/foo/ ../../path/to/release/
cygport foo-0.9.4-1 finish
rm -f *.gz *.bz2
cvs rm foo-0.9.3-1.cygport foo-0.9.3-1.src.patch
cvs add foo-0.9.4-1.*
cvs ci
Yaakov
Cygwin Ports
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHSSnWpiWmPGlmQSMRCCz6AKDv9jVC/h5Hh6HylgW+wKPdUNq4nwCguLxm
KPbkq4OFe7QgfhwEIM3sQUM=
=crNt
-----END PGP SIGNATURE-----
