← Back to team overview

coapp-developers team mailing list archive

Re: Implicit CoApp Package Composition Rules

 

Although, thinking further, if we had implicit rules, we could change them in the package manager and it would affect all packages--we could change our minds and not have to rebuild packages to make changes to layout.

g

From: coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Garrett Serack
Sent: Tuesday, April 12, 2011 8:02 AM
To: Eric Schultz (wwahammy@xxxxxxxxx); coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: [Coapp-developers] Implicit CoApp Package Composition Rules

Hey Eric,

I'm just implementing the package composition stuff right now; I'm wondering if there should be some implicit rules (that aren't stored in the package file), or if we should just automatically create the implicit rules in autopackage.

For example, the symlink for the {$CANONICALPACKAGEDIR} to the {$PACKAGEDIR) ... (ie c:\apps\httpd => c:\apps\.installed\Apache Software Foundation\httpd\ )

Hmm. Just saying it makes me think we should put it into autopackage, and I shouldn't assume anything at all.

Thoughts?

G

[Description: Description: Description: fearthecowboy]<http://fearthecowboy.com/>

Garrett Serack | Microsoft Open Source Software Developer | Microsoft Corporation
Office:(425)706-7939                                       email/messenger: garretts@xxxxxxxxxxxxx<mailto:garretts@xxxxxxxxxxxxx>
blog: http://fearthecowboy.com<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.




GIF image


References