Re: [Coapp-developers] misc

We're actually writing the core so that it can be consumed by both GUI and CLI clients; pretty much everything is being written in this way so that we've got maximum flexibility. As for abbreviations, I was thinking that exact same thing. I'll see about adding that sometime soon. We've got so

Re: [Coapp-developers] Requiring non-CoApp MSI's

We talked about this at the summit. We definitely need to handle this-I suspect that we will have small set of special cases in the short run (.NET framework, C++ redist libraries). In the longer run, I'd we had talked about an 'alien-abduction' tool that consumes & repackages existing installe

Re: [Coapp-developers] cli command syntax

Hmm. Good Call. G -Original Message- From: coapp-developers-bounces+garretts=microsoft@lists.launchpad.net [mailto:coapp-developers-bounces+garretts=microsoft@lists.launchpad.net] On Behalf Of Mark Stone Sent: Tuesday, June 29, 2010 12:33 AM To: coapp-developers@lists.launchpad

Re: [Coapp-developers] misc

On 6/28/2010 8:39 PM, Rivera, Rafael wrote: Hi Laura, Regarding #2: This came up during the summit and we all agreed there would be a "portable" installation flag/command. This would allow you to deploy an application to a custom location, like a USB flash memory. Surprise! :) /rafael On 6/28/

Re: [Coapp-developers] misc

Hi Laura, Regarding #2: This came up during the summit and we all agreed there would be a "portable" installation flag/command. This would allow you to deploy an application to a custom location, like a USB flash memory. Surprise! :) /rafael On 6/28/2010 7:11 PM, m...@distasis.com wrote > Second

[Coapp-developers] misc

There were 3 topics I wanted to bring up for possible further discussion while things are still in the planning stages. The first was to ask that there would be a command line interface for any tools that would be created. Just read the post about cli command syntax, so hopefully that topic's cov

[Coapp-developers] CoApp in the first 90 days

(cross-posted from my blog) It has been nearly three months since launching the CoApp project, and in that time I've been absolutely amazed at the response that we've gotten, and the community folks that have jump

Re: [Coapp-developers] cli command syntax

You are going to want something like: coapp --dep lists the other packages on which the named package is dependent. On Sun, Jun 27, 2010 at 5:11 PM, Garrett Serack wrote: > Here is my proposed command line syntax for the CoApp cli. > > > > I’m sure that it’s not 100% complete, but I think it sho

[Coapp-developers] Requiring non-CoApp MSI's

I haven't seen this come up in the mailing lists or the wiki but I'm wondering what thought has been put into the usage scenario where a package requires software non-CoApp. The main example in my mind would be a package that requires the newest version of the .NET Framework but the user doesn't cu

Re: [Coapp-developers] cli command syntax

Well truthfully, I know we need to handle those concepts; However, I'm not sure that I know I've got them correctly designed. But, point taken. I'll look at removing them for the short term until we see it clearer. G -Original Message- From: Adam Kennedy [mailto:adamkennedybac...@gma