https://sourceware.org/bugzilla/show_bug.cgi?id=16790
--- Comment #9 from Corinna Vinschen <corinna at vinschen dot de> --- (In reply to Corinna Vinschen from comment #8) > (In reply to Nick Clifton from comment #7) > > > I'm just wondering if the default-manifest shouldn't then be made > > > into its own package, independent of binutils and GCC, so that we > > > can update the default manifest if a new Windows comes out, without > > > having to update binutils or GCC packages as well. > > > > I guess that this could happen, Although maybe it could become part of > > the Cygwin and MinGW projects instead ? I assume that they are the only > > ones that need the default manifest. Hmm, that does mean keeping two > > copies of the manifest in sync in different projects, which is not > > ideal. So maybe a separate project would be better. How does one go > > about creating a new project anyway ? > > Easy: I'll create a new cygwin-apps project in the cygwin-apps CVS > repo on sourceware called "windows-default-manifest" od some > such, and I will create a Cygwin package from there. I put > it under a freeware license so everybody who wants to pick it > up is free to do so. I'll keep it up-to-date as far as new > Windows version come along. I created the project, so we can take the next steps: cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps co windows-default-manifest Corinna -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
