[udig-devel] NSIS 2.4.6 build dependency

[Jody Garnett]

I would like to ask PSC approval for the following build dependency:
- NSIS 2.46

Please consider this a quick request to specifically use NSIS 2.46 - when considering a later version we will send another email just like this one.

[Frank Gasdorf]

2013/6/13 Jody Garnett <jody.garnett at gmail.com>

Post by Jody Garnett
approval

1+ with some side-notes:
* 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?
* 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.refractions.net/pipermail/udig-devel/attachments/20130613/5526cf6a/attachment-0001.html>

[Jody Garnett]

Bah apparently this was the wrong move, I was supposed to ask wayne on a different list or something.

Wayne this migration process is killing us, if we can perhaps arrange a Skype time to sort out how to proceed.

I tried to do:
a) one example build dependency (this NSIS thing)
b) one example dependency dependency (JTS)

And neither is moving *fast*, indeed they are held up because I want to submit links to code I did not package myself (rather than upload a zip).

Can you think of a way we can light a fire under this process? We have a lot of dependencies to submit, and we need a repository and to get our build back in order.
--
Jody Garnett

2013/6/13 Jody Garnett <jody.garnett at gmail.com (mailto:jody.garnett at gmail.com)>

Post by Jody Garnett
approval

* 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?
* 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.
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.refractions.net/pipermail/udig-devel/attachments/20130614/49b06fbf/attachment.html>