| Previous · Next | |
| User | Message |
|
colink
|
Date: 7/7/2008 9:21 pm · Subject: Multiple package files · Rating: 0
Now that we're using package files for updating templates, it seems like we need to be more careful about stomping templates between packages. For example, if two different packages have the same template in them, whichever one gets installed last wins. What order are the packages installed (alphabetical, random or other)? Do we need some checks and balances in place to make sure that template bugs don't get fixed and then unfixed? |
| Back to Top |
Rate [ | ]
|
|
preaction
|
Date: 7/7/2008 9:59 pm · Subject: Re: Multiple package files · Rating: 0
Packages themselves solve the problem: Only later revisions of an asset that is in a package are moved to the system. However, if two people fix a bug in the same template, this problem could happen. I've been doing this: 1) Make a package out of a Folder under the Import Node 2) Make my changes 3) Put the package in the upgrade If I need to change something again, I 1) resetdev 2) Make my changes 3) Make the package out of the Folder again 4) Overwrite the existing package with my new package My method, however, adds things to the webgui tarball that don't change from one version to another. Perhaps we need to simply restrict packages to the smallest possible set of changes? The RFE for a link in the Asset Manager to "Export as Package" a single asset would be a boon in this regard. |
| Back to Top |
Rate [ | ]
|
