[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Group policy install, dictionary

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 15 Sep 2009 18:59:53 +0200

On 15.09.2009 15:13, Chris Watson wrote:
> Stefan Küng wrote:
>>> If I used this method to create a transform against say version 1.6.3,
>>> can I safely use the same transform against the 1.6.4, 1.6.5, etc
>>> installers, or should I follow that procedure to create a new transform
>>> each time? I'd rather not just edit the original msi and deploy that
>>> because editing it breaks the digital signature now all the installers
>>> are signed.
>> Sorry, I don't know enough about transforms to confirm or deny this.
>> You'd have to try it yourself if that transform is version independent
>> or not.
>> Stefan
> Yes you can do this with transforms. There are options for marking them
> valid only for particular ProductCodes, version numbers, etc. Orca shows
> a transform made against 1.6.3 successfully transforming the 1.6.5 msi
> database, and this has been confirmed in deployment tests too. I decided
> to mark my transform only valid for the UpgradeCode found in all the
> TSVN msis, which I'm assuming will remain constant throughout all TSVN
> versions as TSVN is TSVN is TSVN...?

Yes, the upgradecode will remain the same, as it has to be according to
the msi rules.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-15 19:00:01 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.