Prev: test
Next: Cloud computing: a definition & an example
From: Nicodemus on 10 Apr 2010 17:59
Too little and so late



Craig <netburgher(a)REMOVEgmail.com> wrote in
news:hpqre1$m5b$1(a)news.eternal-september.org:

> Long & short: Garrett Serak of MS got the go-ahead to set up a
F/OSS
> community project to develop a package-management system similar
to
> those used by F/OSS OSes (think debian's apt or Red Hat's RPM).
No
> more dependency-hell, upgrade disasters & the like.
>
> Pretty tall order.
>
> fyi,
>
> From Ars Technica's Ryan Paul:
>>
>> Microsoft developer Garrett Serack has identified a compelling
>> solution to this problem. He is launching a new project to
build a
>> package management system for Windows with the aim of radically
>> simplifying installation of popular open source software on
>> Microsoft's platform. He calls it the Common Open Source
Application
>> Publishing Platform (CoApp).
>
> <http://arstechnica.com/open-source/news/2010/04/microsoft-
offers-much-
> needed-fix-for-windows-oss-development.ars>
>
> From Garrett Serak's announcement, CoApps will:
>
> > # Provide a distributed, community driven package management
system
> > for open source applications on the Windows Platform
> > # Handle multiple versions of binaries using WinSxS (I know,
even
> > the
> > mention of side-by-side components evokes fear, anger and
the
> > desire to go off-diet, but bear with me, I think we�ve got a
> > solution), including multiple copies of the same version of
the
> > same library, compiled with different compilers.
> > # Support 64 bit and 32 bit systems, without hassle or
collisions.
> > # Place binaries, libraries and header files in a logical and
> > consistent location.
> > # Have tools and methods for handling dependencies.
> > # Create reliable installer packages (MSIs) for installing
open
> > source software.
> > # Facilitate sharing of components and allow multiple projects
to
> > easily both participate and consume them.
> > # Allow for upgrades and patching of both libraries and
> > applications.
> > # Be Windows developer friendly. No forcing of building using
> > �make�,
> > but rather taking advantage of the nifty IDEs we already
have.
> > # Also be Windows admin friendly. Even if it�s open source,
you
> > shouldn�t have to be a developer to put Open Source
applications
> > on Windows.
>
> <http://blogs.msdn.com/garretts/archive/2010/03/31/the-common-
opensourc
> e-application-publishing-platform-coapp.aspx>
>

 | 
Pages: 1
Prev: test
Next: Cloud computing: a definition & an example