Robert Collins wrote:
But they didn't really pursue this too strongly -- instead, they focused
on attempting to make the transition smooth ('autoupdate', etc). They
ignored the network-stasis effects (essentially, a classic 'deadlock'
problem: you first, no you first...)
Yes, and IMO a nutso
On Sat, 2003-11-08 at 14:28, cwilson wrote:
> > It'd probably be wise to integrate this with setup.exe so you would
> > have the option to install packages in a non-standard place.
>
> Oh god no. "Click here to automatically fsck-up all the binaries I just
> installed" THAT's a GREAT idea!
cwilson wrote:
So that YOU don't have to? (And wait. What are the current cygwin
maintainers doing so badly that you want to take over and redo their
jobs for them?)
Look. Patches should go back to the upstream package. There should not
be a bunch of extant, uncommitted patches laying about
Edward S. Peschko wrote:
See, to build a shared lib, you really really need to use libtool-devel,
which is libtool-1.5, and which requires automake > 1.5.0 and autoconf >
2.50. However, those packages are just now -- after 1.5 years -- coming
into widespread use, because
that's just silly. Gnu
> See, to build a shared lib, you really really need to use libtool-devel,
> which is libtool-1.5, and which requires automake > 1.5.0 and autoconf >
> 2.50. However, those packages are just now -- after 1.5 years -- coming
> into widespread use, because
>
> 1) autoconf 2.5x is in some ways
Charles Wilson wrote:
1) most (upstream) maintainers want small, easily digestible patches
-- so mega-patches must be split up into functional units.
See, for instance, this week's libtool-patches mailing list.
http://mail.gnu.org/archive/html/libtool-patches/2003-11/index.html
--
Chuck
--
Uns
Edward S. Peschko wrote:
I was curious - exactly what is the process to submit cygwin patches to the respective
projects that support cygwin as a target?
I've been integrating cygwin into the build for the OSes I support, and I find that there
are hundreds of thousands of lines of patches for cygw
I was curious - exactly what is the process to submit cygwin patches to the respective
projects that support cygwin as a target?
I've been integrating cygwin into the build for the OSes I support, and I find that
there
are hundreds of thousands of lines of patches for cygwin (around 400k). Som
8 matches
Mail list logo
