Thinking about this another way: >From my Debian box, I want to be able to *apt-get coapp-build
co-buildpkg mycoolapplication *So far, only the NSIS installer can build a Windows installer from a Linux-based host. On Thu, May 6, 2010 at 6:35 AM, Garrett Serack <[email protected]>wrote: > True, True. True. True. > > > 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. > > > -----Original Message----- > From: > coapp-developers-bounces+garretts=microsoft....@lists.launchpad.net[mailto: > coapp-developers-bounces+garretts <coapp-developers-bounces%2Bgarretts>= > [email protected]] On Behalf Of William A. Rowe Jr. > Sent: Wednesday, May 05, 2010 12:20 PM > To: Pierre Joye > Cc: [email protected] > Subject: Re: [Coapp-developers] What packages do you want to see? > > On 5/5/2010 12:22 PM, Pierre Joye wrote: > > On Wed, May 5, 2010 at 7:10 PM, Olaf van der Spek <[email protected]> > wrote: > > > >> Who said CoApp won't support first-party builds? > > > > Nobody, I call that a discussion. > > CoApp the distribution wouldn't be likely to trust third party builds, but > build from documented/legible source code. > > CoApp the project is unlikely to "convince" the projects that this specific > set of build options is the "one right way", and (speaking from 10+ years of > experience) most are unlikely to adopt CoApp conventions. And why should > they? > > Like all Linux or BSD distributions, there isn't "one right way" - and each > distribution chooses to do things as they see fit, including rearranging the > binary artifacts and files of the package, optimizing build flags, and > providing integration stubs that make using the package "easier" (for very > loose definitions of "easier"). > > Most importantly, solving the code signing problem is not trivial. CoApp > the distribution would never sign a third party's build as "trusted". They > would sign it themselves. But this causes their fault data to go to the > author and miss the collection of bug reporting available to the CoApp team. > (And visa versa, so I'm guessing that Garrett intends for CoApp to proxy > crash information to the original developers that arrives in the CoApp > stream). > > That doesn't mean that CoApp the toolchain can't offer all sorts of tools > for the authors and projects to use and come to rely on :) > > _______________________________________________ > Mailing list: > https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers> > More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: > https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers> > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
