> > 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
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
> 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
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
> woul
-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
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-au
-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
> "rollu
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
-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
> (http://sources.gentoo.org/
-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 a
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 apply them all
> at
> package build time.
Okay,
> Andrew, please post one of your .cygports that actually requires the
> src_prep_fini_hook(). I'd like to reach a resolution on this (these)
> issues, so I can either drop the patches entirely or get some
> replacement/reimplementation in cygport.
OK, here's how I use it.
Several of my packages
Andrew Schulman wrote:
> As I explained in the thread referenced above, src_patch_hook() and
> src_unpack_hook() are not adequate substitutes for src_prep_fini_hook(),
> because
> both of the former act *before* origsrc is mirrored to src. So, using them it
> is not possible to make changes to sr
> 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
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 patch
-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.
* autotools.cygcla
16 matches
Mail list logo
