If I understand the implications correctly, one would need a three
- sign the setup.ini file with a key, in place - put up a public key to check against, somewhere else - point setup.exe to the location of the public key Given that all we want are the dependencies (the package is empty),
Please remember to update the log on the wiki page when you succeed -
Hi Claus, point change to adapt properly: this is starting to look ridiculous (one has to put in more administrative information than one saves from not having to specify the dependencies by hand..). However, the dependency package is very useful, so if its not too much work, it would be useful. the value of this log comes from being
applied from scratch (when just updating, it is easy to miss something).
I am keeping an up to date list of what I do and what works, so will combine it in once I have a working build. Thanks Neil ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ==============================================================================