Yaakov (Cygwin Ports) wrote:
They were called rollup patches. T.E.D. releases patches roughly every
week, and then every month (or two, or three), he combines all patches
dating back to an official release into a rollup patch -- and these
rollup patches are in the shar-archive-auto-apply
Yaakov (Cygwin Ports) wrote:
It only breaks the ABI (B?) if you do it the way you suggested:
http://cygwin.com/ml/cygwin/2008-05/msg00038.html
Yes, the concept is the same: ABI breakage affects previously-built
source packages but doesn't necessarily break API (IOW the .cygport
wouldn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Even the rollup patch?
ftp://invisible-island.net/${PN}/${PV}/${PN}-${PV}-20060909-patch.sh.bz2
Yes.
It only breaks the ABI (B?) if you do it the way you suggested:
http://cygwin.com/ml/cygwin/2008-05/msg00038.html
Yes,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
They were called rollup patches. T.E.D. releases patches roughly every
week, and then every month (or two, or three), he combines all patches
dating back to an official release into a rollup patch -- and these
rollup
Yaakov (Cygwin Ports) wrote:
Charles Wilson wrote:
a) my example, ncurses, has a LOT (50 or so) official patches
b) they are all gz-compressed; cygport might not support compressed
patches in PATCH_URI
Compressed single patches are supported in PATCH_URI since 0.3.5.
Good to know. I
