Re: Conditionally build different versions of a package?
Re: Conditionally build different versions of a package?
- Subject: Re: Conditionally build different versions of a package?
- From: Kevin Brock <email@hidden>
- Date: Mon, 12 Oct 2009 15:35:23 -0700
marc hoffman wrote:
Kevin,
Step 2 is complicated by the fact that PM may change the internal
names of the XML files in the package if you change something. If
you change things through the GUI, you need to verify the names of
the files the script is processing. You also need to watch out for
this if you've got your projects in a SCM system. You might make an
apparently trivial change and then find out there are a number of
files that need to be added and/or deleted from the SCM repository...
thanx. so the real answer is that i wasn't missing anything, and
there's no official way to do it, besides manually messing with the
raw files - i was afraid of that. guess for the short term i'll try to
go with two separate projects, then :(.
it's a shame, really. if only the random renaming/reordering of the
files wouldn't happen, this would he halfway feasible (ie, keeping the
folder in almost-sync thru, say, Araxis Merge)...
I may have made the renaming sound worse than it is... Generally it's
only an issue when you add or remove something.
You could probably write the scripts so that they figure out which XML
file is which component based on the contents, instead of hard-coding
the file names.
Kevin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden