Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-devel] PSC decision on NSIS installer
Hi Frank I am going to answer your side-notes over here:
* NSIS has some basic scripts out of the box but is possible to extent with own scripts. Do we have self-contributed scripts in our code-base (nsh) or even macros in nsi file copied from somewhere else? 
We have an installer script contributed directly to the project by Chris Holmes. 
* What about nsh-plugins and review processes for build dependencies in the future. Do we need run an IP dependency request for each script? I guess these scripts are part of the resulting installer and therefore I'm not sure about IP issues, if uDIG is packaged this way.
This "build-dependency" request is specifically to use one version of NSIS in our build process. I have to submit a second request (and supply the source code) for our generated installer to distribute the bits and bobs of the NSIS code.
-- 
Jody Garnett

On Tuesday, 11 June 2013 at 6:57 PM, Jody Garnett wrote:

Wayne do you have any guidance on this one?

I have a confusing request from Sharon with respect to our use of NSIS installer. She asks to be pointed at the decision by the PSC to use NSIS as a build tool.

There are two ways for me to read this:

1) Request to point to a historical discussion?

As such it kind of predates the formation of a PSC.
The installer was originally contributed by Chris Holmes for uDig 0.4.

Searching down the details:

Aside: thanks to Chris Holmes

2) Request to interact with the Eclipse Developer Portal

She may also be asking us to use the developer portal to vote on the dependency request (i.e. I have submitted it as a request to the IP team, perhaps the next step is for the PSC to approve my request?)


-- 
Jody Garnett

Back to the top