Yaakov (Cygwin Ports) wrote:
| Is there a way I can get Cygport to generate this patch for me?
You need to put these files into foo-ver-rel/CYGWIN-PATCHES/.
I actually stumbled across that earlier, but I convinced myself it
couldn't be the right way to do it.
foo-ver-rel doesn't exist unti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Warren Young wrote:
| Is there a way I can get Cygport to generate this patch for me? It
| seems like it should be able to take the source package, the README, and
| the setup.hint and generate the patch during the prep stage. I can't
| see how to
Dr. Volker Zell wrote:
Builds fine from source, but the cygwin specific patch has 0 bytes. So
there is no README and the .hint files are missing
Yeah, I've been meaning to ask about that...
Is there a way I can get Cygport to generate this patch for me? It
seems like it should be able to ta
> Warren Young writes:
> Taking over maintainership of this package from Max Bowsher. Ported
> from g-b-s to cygport and updated from 1.95.8 to 2.0.1, so I'd like at
> least one GTG before I post the RFU message.
Builds fine from source, but the cygwin specific patch has 0 bytes
Taking over maintainership of this package from Max Bowsher. Ported
from g-b-s to cygport and updated from 1.95.8 to 2.0.1, so I'd like at
least one GTG before I post the RFU message.
Also, we need a ruling on what to do with the existing expat 1.x stuff.
It seems there's an ABI difference b
