Re: sourceware and git

[Corinna Vinschen <vinschen@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 2414 bytes --]

On Jul 30 22:22, Christopher Faylor wrote:
> On Wed, Jul 30, 2014 at 06:41:25PM -0500, Yaakov Selkowitz wrote:
> >On Wed, 2014-07-30 at 17:33 -0400, Christopher Faylor wrote:
> >> As far as tagging is concerned, I don't see any reason why newlib
> >> should be tagged when cygwin is tagged.  Cygwin shouldn't care about
> >> newlib tags.
> >
> >What I don't understand yet is why our situation is different than
> >binutils-gdb, the two of which also have separate release schedules and
> >yet share enough code that they chose to use a single repository.  Given
> >that, IIUC:
> 
> I don't care about newlib/libgloss.  The need for libgloss is enough for
> me to withdraw that newlib should be standalone.
> 
> The difference here is that I'm involved with cygwin.  I didn't care
> about binutils+gdb so I didn't weigh in.  I'm weighing in now.
> 
> >* newlib and libgloss are developed in tandem;
> >
> >* newlib and libgloss are meant to be built together;
> >
> >* newlib and libgloss require the top-level configury in order to build;
> >
> >then wouldn't the most straightforward (and reliable) method for
> >newlib/libgloss be to have a single git repo matching the layout of cvs
> >co newlib?
> >
> >As for cygwin's usage of newlib, since pulling in newlib would end up
> >including libgloss and the top level configury, the only difference I
> >see between a joint newlib/libgloss/cygwin repo and a separate cygwin
> >repo would be that the former would not require any changes to the
> >cygwin build system, where the latter would.
> 
> I have already made the changes for cygwin.  Is this not sinking in
> somehow?  I was trying to make cygwin like most other GNU projects out
> there, unencumbered by decades of top-level build accretion, relying on
> only one other library, similar to the way other projects do it.
> 
> Anyway, nevermind.  I see that I'm in the minority.  My changes and git
> repository are withdrawn.  Do what you like.

Hmm, that wasn't exactly what I was looking for.  I was just trying to
make sure that the git repo for Cygwin contains all of Cygwin, and that
includes newlib.  It's not just an external library, it's an inherent
part of Cygwin.  You can't build Cygwin without newlib and you can't
build a standalone newlib for Cygwin without the Cygwin sources.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]