[Coapp-developers] CO_INSTALL_PROPERTIES.type values
Eric,
I've created an enum for the possible values for CO_INSTALL_PROPERTIES.type
field (CoApp.Toolkit.Engine.CompositionAction); when you get a chance, can you
make sure that the values for that field match that:
public enum CompositionAction {
SymlinkFile,
SymlinkFolder,
Shortcut,
}
That'll make sure the Composition Rules parse correctly :D
[Description: Description: Description:
fearthecowboy]http://fearthecowboy.com/
Garrett Serack | Microsoft Open Source Software Developer | Microsoft
Corporation
Office:(425)706-7939 email/messenger:
garre...@microsoft.commailto:garre...@microsoft.com
blog: http://fearthecowboy.comhttp://fearthecowboy.com/
twitter: @fearthecowboyhttp://twitter.com/fearthecowboy
I don't make the software you use; I make the software you use better on
Windows.
inline: image001.gif___
Mailing list: https://launchpad.net/~coapp-developers
Post to : coapp-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~coapp-developers
More help : https://help.launchpad.net/ListHelp
Re: [Coapp-developers] Ninite
Ninite just puts together a collection of known-working-installers. They pretty much expose the product discovery scenario, and streamline the installation but that's pretty much it. 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: Saturday, April 09, 2011 11:31 AM To: coapp-developers@lists.launchpad.net Subject: [Coapp-developers] Ninite This looks like something we ought to be paying attention to, and have an opinion on. I haven't dug into the details yet, having just stumbled across this story, but it has some clear similarities to CoApp, and if its part of BizSpark then it has some degree of backing from Microsoft: http://mashable.com/2011/04/09/ninite/ -Mark ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
Re: [Coapp-developers] Simulating Symlinks on Windows XP
I think it's a testament to Wine if CoApp works on it; less so, vice-versa. I think when we get to CoApp V2 it'll be a bit easier. G From: coapp-developers-bounces+garretts=microsoft@lists.launchpad.net [mailto:coapp-developers-bounces+garretts=microsoft@lists.launchpad.net] On Behalf Of Eric Schultz Sent: Saturday, April 09, 2011 12:44 PM To: William A. Rowe Jr. Cc: coapp-developers@lists.launchpad.net Subject: Re: [Coapp-developers] Simulating Symlinks on Windows XP I know it sounds crazy at first. Consider though the situation of a Windows-only program with dependencies on CoApp packages that someone wants to install on Linux. It would be nice if installing that didn't fail. Again, it's not a particularly pressing issue just something to think about. Eric On Thu, Apr 7, 2011 at 8:34 PM, William A. Rowe Jr. wmr...@gmail.commailto:wmr...@gmail.com wrote: On 4/7/2011 8:06 PM, Eric Schultz wrote: I wonder what effect all this will have on CoApp package installation on WINE. Obviously that not a pressing issue but its probably something to consider going forward. . Entire point of CoApp - running OSS packages natively Let's see, what is it going to take to run coapp on wine on sfu on windows? EBYDESIGN? ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.netmailto:coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
Re: [Coapp-developers] Superceeding Packages...
I think it should tell something like You already have a newer version installed and ask if you want to use the old one as the new “current”. Hälsningar, Fredrik Sundqvist 2011/4/12 Garrett Serack garre...@microsoft.com Howdy, I’m just working on the package composition support right now… If you remove a package, and there is a previous version still installed, I’m thinking that it becomes the “current” version automatically. I can also easily add command-line support to make an arbitrary given version the “current” one, regardless of which is the most recent. The question is, what should the default behavior be when you install an older version when you have a newer on installed? Do I keep the most recent as the current unless you specifically state that you want **this specific version I’m installing** as the new “current”? [image: Description: Description: Description: fearthecowboy]http://fearthecowboy.com/ *Garrett* *Serack* | Microsoft Open Source Software Developer | *Microsoft Corporation Office*:(425)706-7939 *email*/* messenger*: garre...@microsoft.com *blog*: http://fearthecowboy.com * twitter*: @fearthecowboy http://twitter.com/fearthecowboy *I don't make the software you use; I make the software you use better on Windows.*** ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp image001.gif___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
Re: [Coapp-developers] Superceeding Packages...
Yeah, that is easy enough to do, and certainly the GUI should be really up front about that. G From: Fredrik Sundqvist [mailto:fsundqv...@gmail.com] Sent: Tuesday, April 12, 2011 11:41 AM To: Garrett Serack Cc: coapp-developers@lists.launchpad.net Subject: Re: [Coapp-developers] Superceeding Packages... I think it should tell something like You already have a newer version installed and ask if you want to use the old one as the new current. Hälsningar, Fredrik Sundqvist 2011/4/12 Garrett Serack garre...@microsoft.commailto:garre...@microsoft.com Howdy, I'm just working on the package composition support right now... If you remove a package, and there is a previous version still installed, I'm thinking that it becomes the current version automatically. I can also easily add command-line support to make an arbitrary given version the current one, regardless of which is the most recent. The question is, what should the default behavior be when you install an older version when you have a newer on installed? Do I keep the most recent as the current unless you specifically state that you want *this specific version I'm installing* as the new current? [Description: Description: Description: fearthecowboy]http://fearthecowboy.com/ Garrett Serack | Microsoft Open Source Software Developer | Microsoft Corporation Office:(425)706-7939 email/messenger: garre...@microsoft.commailto:garre...@microsoft.com blog: http://fearthecowboy.comhttp://fearthecowboy.com/ twitter: @fearthecowboyhttp://twitter.com/fearthecowboy I don't make the software you use; I make the software you use better on Windows. ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.netmailto:coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp inline: image001.gif___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
