Having a standardized repository for .NET libraries, with installation and dependency checking tools, looks like a good idea. It could work exactly in similar way to cpan / ruby gems. We had a little discussion about it in our community and there was a loose idea of using google code for managing and storing all there projects. Such global repository could also store binaries I guess.
2007/1/9, Bouk, Nathan <[EMAIL PROTECTED]>: > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miguel de Icaza > Sent: Monday, January 08, 2007 1:04 PM > To: Rafael Teixeira > Cc: [email protected]; "Andrés G. Aragoneses [ knocte ]" > Subject: Re: [Mono-list] C# command line parsing library > > >This goes to a more general issue: I think we were too lax accepting new > >APIs that were evolving into the Mono core, which is why these days the > >answer to "Could you bundle MyFavoriteLibraryThatIJustDeveloped in Mono" > >is "no". > > > Maybe some kind of Mono-CPAN (CMAN is taken, some clustering project) would > give these things a place to live outside of the Mono tree? > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list > -- Kamil Skalski http://nazgul.omega.pl _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
