I've updated the following three patches to make them
apply cleanly against setup-2.599
6689-goossens-rev1-rh.patch
6688-switch-p-rh.patch
854-peschko-cmdlines-rh.patch
I've also attached a series that can be used withe
quilt to manage application and removal of the patches:
Please note that
Charles Wilson wrote on 23 July 2008 03:01:
Charles Wilson wrote:
Brian Dessent wrote:
Charles Wilson wrote:
which are under source control in the setup repository really should
/not/ be stored in CVS. They are regenerated every time you run
doconfigure, anyway.
It makes sense to not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| When 1.7 goes gold, the idea is to install over an 1.5 install. Or not.
| It's the choice of the user. Installing over 1.5 is supported by the
| base-cygwin package, which is supposed to convert the registry mount
|
On Jul 23 12:25, Yaakov (Cygwin Ports) wrote:
Corinna Vinschen wrote:
| When 1.7 goes gold, the idea is to install over an 1.5 install. Or not.
| It's the choice of the user.
The advantage of starting fresh with 1.7 would allow us to dump a lot
of obsolete packages from the distro [...]
Ralph Hempel wrote:
I've updated the following three patches to make them
apply cleanly against setup-2.599
They also apply cleanly on setup-2.592-1.7special...
Ralph
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As we start preparing for 1.7, I know that until now the focus has been
on the development of Cygwin itself. I'll admit that I know little
about Cygwin's internals, and hence have contributed very little to the
DLL itself, but I do very much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I would like to make some proposals as to setting up the development
toolchain for 1.7:
1) binutils
Thanks to cgf, we've got a current binutils available now; I'm not sure
if binutils itself benefits from 1.7 (save the long path handling).
There
