coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

Just for clarity sake:

CoApp will easily support multiple compilers-I think it's not only important to do so for non-CoApp consumers (IE, someone wants to use a CoApp packages with their own software that is not CoApp packaged) but, to make sure that retargeting to new compilers isn't going to be a problem.

When we control the build for a package, this can be handled a couple of different ways:
- Generate project files for a different compiler.. this is pretty easy and ultimately flexible, but probably more work to automate.
- Or Use MSBuild 4.0's ability to drive different  compilers-requires VC10 [even just express] and some one time setup of some compiler data files ... this is probably easier to automate more compilers,

When a developer consumes a shared library (say, zlib), they consume the library by binding to a library that is identified by NAME, PLATFORM (x86/x64), VERSION and PUBLICKEYTOKEN ... the publicKeyToken is derived from the public key of the signing certificate.

So, if the publisher of zlib wants to publish one for VC9 and one for VC10 they have to have two authenticode certificates.  A bit of a pain, yes. But we can have the same version of the library installed for multiple compilers at the same time, and never have a conflict.

I'll go into a lot more detail next week.

G

From: coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Trent Nelson
Sent: Thursday, May 06, 2010 5:26 PM
To: Daniel James
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] What packages do you want to see?

Daniel,

Out of interest, why do you stipulate that you want VC9 builds?

With Python, for example, the version of Visual Studio we build with is fixed for each major version (2.x/3.x).  2.5.x uses VS2005, 2.6.x uses 2008, etc.  One of the reasons we do this is because it allows packages and libraries to all build and test against a common version (even if it's not the most recent version of VS; later 2.5.x releases of Python were still being built with VS2005, even though VS2008 had been readily available for over a year).

As a CoApp consumer (sys admin in your user story) - do you have a requirement to build with a specific version of VS, even if it differs from what a project was originally intended to be built with?

And to the CoApp developers: do we want to provide users with the ability to compile these open source projects from scratch using whatever version compiler tool chain they want?  Perhaps something analogous to FreeBSD ports, which are built from scratch using whatever compiler you want, versus FreeBSD binary packages, which are pre-built using whatever the system compiler is at the time.

I think user stories/use cases are going to become increasingly important in the coming weeks and months ;-)  I'll throw my hat into the circle and offer to be the 'user story collator', unless someone else is dying to do it.  A wiki page dedicated to user stories is a good first step, IMO.  Thoughts/objections?

                Trent.

From: coapp-developers-bounces+trent=snakebite.org@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+trent=snakebite.org@xxxxxxxxxxxxxxxxxxx] On Behalf Of Garrett Serack
Sent: 07 May 2010 04:33
To: Michael Herndon; Daniel James
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] What packages do you want to see?

I love user stories from anywhere....


Yeah, post them here... eventually they'll end up on their way to somewhere useful ;D

G


Garrett Serack | Open Source Software Developer | Microsoft Corporation
I don't make the software you use; I make the software you use better on Windows.

From: mherndon@xxxxxxxxxxxx [mailto:mherndon@xxxxxxxxxxxx] On Behalf Of Michael Herndon
Sent: Thursday, May 06, 2010 1:31 PM
To: Daniel James
Cc: Garrett Serack; coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] What packages do you want to see?

should we be recording user stories from various dicussions?

As a pain the @$$ developer, michael would like to use coapp to distribute .net library x

As a site admin nazi, bob would like to use coapp to install a 64 bit build using VC 9 of apache, ruby, python, 64 bit php on servers "sleepyhollow" and "middle earth"

On Wed, May 5, 2010 at 6:32 PM, Daniel James <dnljms@xxxxxxxxx<mailto:dnljms@xxxxxxxxx>> wrote:
On 5 May 2010 15:59, Garrett Serack <garretts@xxxxxxxxxxxxx<mailto:garretts@xxxxxxxxxxxxx>> wrote:
>
> Assuming that CoApp produces a beautifully functioning package manager and ecosystem, what open source packages would you like to see made available for Windows via CoApp?
Libxslt (for xsltproc) and support for XML packages, especially
Docbook, would be very helpful. There isn't really a good solution on
windows at the moment.

Daniel

_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx<mailto:coapp-developers@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
More help   : https://help.launchpad.net/ListHelp



--
Michael Herndon
Senior Developer (mherndon@xxxxxxxx<mailto:mherndon@xxxxxxxx>)
804.767.0083

[connect online]
http://www.opensourceconnections.com
http://www.amptools.net
http://www.linkedin.com/pub/michael-herndon/4/893/23
http://www.facebook.com/amptools.net
http://www.twitter.com/amptools-net