Re: [E-devel] EFL Windows Installer

[Vincent T. <vt...@un...>]

On Fri, 3 Jun 2011, Lionel Orry wrote:

> On Fri, Jun 3, 2011 at 1:25 PM, Vincent Torri <vt...@un...> wrote:
>>
>>
>> On Fri, 3 Jun 2011, Lionel Orry wrote:
>>
>>> On Thu, Jun 2, 2011 at 8:05 AM, Vincent Torri <vt...@un...> wrote:
>>>>
>>>> comments, remarks, ideas, fixes are welcome of course.
>>>>
>>>> Vincent
>>>
>>> Well, here is a series of remarks:
>>>
>>> 2. That may be a personal taste but I think a Makefile would be more
>>> suited than a bash script for the purposes in test.sh. It looks a bit
>>> bloated (no offense, I understand it was not meant for public use but
>>> for your personal use). I could try to make a corresponding makefile.
>>
>> i have no strong opinion, here. If you can write it, no problem for me. I
>> will use it, i think.
>
> I'll give it a try.
>
>>
>>> 3. Did you consider other alternatives than NSIS? It's a good one, but
>>> nowadays the tendency in windows world is to create MSI databases (so
>>> called 'Windows Installer packages") that use Windows Installer to
>>> install themselves. It's a very clean solution, and one tool to create
>>> such installer is Wix (http://wix.sourceforge.net). I've already used
>>> wix in the past and it's an amazing tool, trust me, even though the
>>> XML syntax is a bit scary at first. And it's easy to auto-generate Wix
>>> scripts to automate all this a bit more.
>>
>> I don't like msi installers as you can install the software only if you have
>> admin privilegies :
>>
>> http://wix.sourceforge.net/manual-wix3/authoring_first_file.htm
>>
>> step 5, it is said:
>>
>> "Note that msi packages requires administrative privileges in order to
>> install correctly"
>>
>> so for me, it's not acceptable.
>
> I didn't think it was a constraint for you, but if it is, indeed you
> can't use MSI packages. So let's forget my suggestion.
>
> Aside note: if you don't want to require admin privileges, you should
> definitely avoid to install stuff in Program Files or equivalent, but
> in the user space. Up to XP that would work, but UAC and other new
> security policies in newer versions will cause you great trouble. So
> maybe you should change the default install path to a more sensible
> location, but I'm not sure which one and how to express it... The NSIS
> wiki and docs may have tips about that.

another thing to take into account is if the installer is used to code 
with the EFL and mingw, the path in which the EFL are installed must not 
contain white spaces. Maybe I should use by default c:\EFL


Vincent