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: marc hoffman <email@hidden>
- Date: Tue, 13 Oct 2009 00:04:51 +0200
Kevin,
that's a very helpful anser ;)
It's accurate though... One approach might be
1) Build a package that has everything
2) Write a script that goes through the XML files and removes source
targets & non-trial stuff from the generated XML, and deletes the
corresponding packages if it's a trial distribution.
Only two steps, but number 2 requires some work.
The *simple* solution is to have two different installer projects,
and manually coordinate them.
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)...
thanx,
marc
_______________________________________________
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