Okay, so these are (mostly) your own custom patches needed to port the
code to cygwin, and not official patches from somewhere else
Correct. Or anyway, they're patches that aren't included in the source tarball,
and that I maintain separately as discrete patch files.
Effectively, you're
2008/10/28 Yaakov (Cygwin Ports):
I've just made cygport-0.9.3 available in release-2 with the following
changes:
* PV is now an array; members 1-* replace PVP[].
* foo_CONTENTS can now be used in place of PKG_CONTENTS[].
* cygtest(): Doesn't exit when tests fail.
* autotools.cygclass
Several of my packages require multiple patches to compile and run properly
in
Cygwin. Instead of maintaining them all together as One Big Patch, I find
it
easier to manage them as individual, discrete patch files, and apply them
all at
package build time.
I do that all the
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew Schulman wrote:
Several of my packages require multiple patches to compile and run properly in
Cygwin. Instead of maintaining them all together as One Big Patch, I find it
easier to manage them as individual, discrete patch files, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Okay, so these are (mostly) your own custom patches needed to port the
code to cygwin, and not official patches from somewhere else, like
1) bugfixes taken wholesale from another distro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've just made cygport-0.9.3 available in release-2 with the following
changes:
* PV is now an array; members 1-* replace PVP[].
* foo_CONTENTS can now be used in place of PKG_CONTENTS[].
* cygtest(): Doesn't exit when tests fail
Yaakov (Cygwin Ports) wrote:
If there are any changes you want to see in cygport, please let me know
ASAP; I would like to have the major changes out of the way soon,
so that cygport isn't a moving target once everything is ready for a 1.7
rebuild.
Forward port of my three remaining patches
If there are any changes you want to see in cygport, please let me know
ASAP;
As I requested before at
http://www.cygwin.com/ml/cygwin-apps/2008-09/msg00070.html, I routinely use
Charles Wilson's patch for src_prep_fini_hook()
(http://www.cygwin.com/ml/cygwin/2007-01/msg00110.html), and would
13 matches
Mail list logo
