Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Samuli Seppänen]

Il 12/12/2016 11:45, Илья Шипицин ha scritto:
>
> I investigated Fedora (we use CentOS/Fedora) and Debian world.
> as for Fedora, it is far from being ready (I'll take care of that)
>
> as for Debian, there's
> http://deb.debian.org/debian/pool/main/n/nsis/
> 
>  >
> so, I installed ubuntu 16.04, added "debian experimental" (the above
> repo), and voila, I compiled openvpn installer.
>
> I think we can move to unicode nsis right after 2.4
>
>
> Excellent news! Once 2.4.0 is out I can again focus on non-release
> critical things, like updating the build VM.
>
>
>
> for future discussion:
>
> a) adopt building guide (on https://openvpn.net) "nsis3 is required"
> b) add "Unicode true" to openvpn.nsi + comment that + provide link to
> web page "a)"
> c) check every nsis plugin whether it supports unicode
> d) release installer
> ...
> z) split installer into several language files + choose language
> automatically (I also do not like manual language selection)

Makes sense.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Илья Шипицин]

2016-12-12 13:46 GMT+05:00 Samuli Seppänen :

> Il 12/12/2016 08:22, Илья Шипицин ha scritto:
>
>>
>>
>> 2016-12-02 11:55 GMT+05:00 Samuli Seppänen > >:
>>
>> Il 02/12/2016 05:54, Илья Шипицин ha scritto:
>>
>> unicode nsis is different from ansi nsis. for example, nsProcess
>> needs
>> different dll.
>>
>>
>> Ok. More research is needed to see what is involved, then.
>>
>> and, unicode nsis is not shipped in most common Linux repo (you
>> need to
>> install it separately).
>>
>>
>> Indeed, that was my impression. So far I've only seen NSIS 2.46 or
>> so in the distribution repositories, and the link I provided talked
>> about NSIS 3.0b or something.
>>
>> taking the above into account, I think, I should repack the above
>> packages as "makensis3" instead of "makensis".
>>
>>
>> You mean creating deb/rpm packages for updated NSIS? I think
>> manually installing updated NSIS would be good enough, if
>> repackaging proves to be too much of an effort.
>>
>>
>> I investigated Fedora (we use CentOS/Fedora) and Debian world.
>> as for Fedora, it is far from being ready (I'll take care of that)
>>
>> as for Debian, there's http://deb.debian.org/debian/pool/main/n/nsis/
>> 
>> so, I installed ubuntu 16.04, added "debian experimental" (the above
>> repo), and voila, I compiled openvpn installer.
>>
>> I think we can move to unicode nsis right after 2.4
>>
>
> Excellent news! Once 2.4.0 is out I can again focus on non-release
> critical things, like updating the build VM.



for future discussion:

a) adopt building guide (on https://openvpn.net) "nsis3 is required"
b) add "Unicode true" to openvpn.nsi + comment that + provide link to web
page "a)"
c) check every nsis plugin whether it supports unicode
d) release installer
...
z) split installer into several language files + choose language
automatically (I also do not like manual language selection)


>
>
> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
>
> irc freenode net: mattock
>
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Samuli Seppänen]

Il 12/12/2016 08:22, Илья Шипицин ha scritto:
>
>
> 2016-12-02 11:55 GMT+05:00 Samuli Seppänen  >:
>
> Il 02/12/2016 05:54, Илья Шипицин ha scritto:
>
> unicode nsis is different from ansi nsis. for example, nsProcess
> needs
> different dll.
>
>
> Ok. More research is needed to see what is involved, then.
>
> and, unicode nsis is not shipped in most common Linux repo (you
> need to
> install it separately).
>
>
> Indeed, that was my impression. So far I've only seen NSIS 2.46 or
> so in the distribution repositories, and the link I provided talked
> about NSIS 3.0b or something.
>
> taking the above into account, I think, I should repack the above
> packages as "makensis3" instead of "makensis".
>
>
> You mean creating deb/rpm packages for updated NSIS? I think
> manually installing updated NSIS would be good enough, if
> repackaging proves to be too much of an effort.
>
>
> I investigated Fedora (we use CentOS/Fedora) and Debian world.
> as for Fedora, it is far from being ready (I'll take care of that)
>
> as for Debian, there's http://deb.debian.org/debian/pool/main/n/nsis/
> 
> so, I installed ubuntu 16.04, added "debian experimental" (the above
> repo), and voila, I compiled openvpn installer.
>
> I think we can move to unicode nsis right after 2.4

Excellent news! Once 2.4.0 is out I can again focus on non-release 
critical things, like updating the build VM.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Илья Шипицин]

2016-12-02 11:55 GMT+05:00 Samuli Seppänen :

> Il 02/12/2016 05:54, Илья Шипицин ha scritto:
>
>> unicode nsis is different from ansi nsis. for example, nsProcess needs
>> different dll.
>>
>
> Ok. More research is needed to see what is involved, then.
>
> and, unicode nsis is not shipped in most common Linux repo (you need to
>> install it separately).
>>
>
> Indeed, that was my impression. So far I've only seen NSIS 2.46 or so in
> the distribution repositories, and the link I provided talked about NSIS
> 3.0b or something.
>
> taking the above into account, I think, I should repack the above
>> packages as "makensis3" instead of "makensis".
>>
>
> You mean creating deb/rpm packages for updated NSIS? I think manually
> installing updated NSIS would be good enough, if repackaging proves to be
> too much of an effort.
>

I investigated Fedora (we use CentOS/Fedora) and Debian world.
as for Fedora, it is far from being ready (I'll take care of that)

as for Debian, there's http://deb.debian.org/debian/pool/main/n/nsis/
so, I installed ubuntu 16.04, added "debian experimental" (the above repo),
and voila, I compiled openvpn installer.

I think we can move to unicode nsis right after 2.4



>
>
>> @mattock, which linux distro do you use for release building ?
>>
>
> Right now Ubuntu 14.04, but I should upgrade to 16.04 soon.
>
>
> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
>
> irc freenode net: mattock
>
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Samuli Seppänen]

Il 02/12/2016 05:54, Илья Шипицин ha scritto:
> unicode nsis is different from ansi nsis. for example, nsProcess needs
> different dll.

Ok. More research is needed to see what is involved, then.

> and, unicode nsis is not shipped in most common Linux repo (you need to
> install it separately).

Indeed, that was my impression. So far I've only seen NSIS 2.46 or so in 
the distribution repositories, and the link I provided talked about NSIS 
3.0b or something.

> taking the above into account, I think, I should repack the above
> packages as "makensis3" instead of "makensis".

You mean creating deb/rpm packages for updated NSIS? I think manually 
installing updated NSIS would be good enough, if repackaging proves to 
be too much of an effort.

>
> @mattock, which linux distro do you use for release building ?

Right now Ubuntu 14.04, but I should upgrade to 16.04 soon.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Илья Шипицин]

2016-12-01 16:40 GMT+05:00 Samuli Seppänen :

> Hi,
>
> Il 30/11/2016 11:58, Илья Шипицин ha scritto:
>
>>
>>
>> (and, yes, I'm going to build multi-language installer, probably
>> right
>> after 2.4 release)
>>
>>
>> This makes sense. Any plans on how you're going to do it?
>>
>>
>>
>> as we do not support windows 2000 anymore, we can easily switch to
>> unicode.
>> there are few questions
>>
>> 1) unicode nsis under linux (we use windows+mingw+nsis unicode, so, I'm
>> not sure about linux)
>>
>>
> Unicode seems to be present in Linux NSIS versions, according to this:
>
> 
>
> The build computers need to be updated to a quite recent NSIS version,
> though.
>


unicode nsis is different from ansi nsis. for example, nsProcess needs
different dll.
and, unicode nsis is not shipped in most common Linux repo (you need to
install it separately).

taking the above into account, I think, I should repack the above packages
as "makensis3" instead of "makensis".

@mattock, which linux distro do you use for release building ?



>
>
> 2) split installer into several language files (as done for openvpn-gui)
>>
>
> We'd also need to detect the language the user is using to select the
> correct one. I personally don't like manual language selector as they add
> one more step to the install process.
>
>
>> 3) test everything
>>
>>
>> it is not difficult, but it is time consuming, I'm afraid we will test
>> it properly before 2.4
>>
>
> The plan is to release 2.5 pretty quickly after 2.4. Also, installer
> changes do not necessarily need to go in sync with OpenVPN releases.
>
>
>> Another internationalization aspect we could improve is how we store
>> translations for OpenVPN-GUI. Editing the resource files directly is
>> clumsy and error-prone, as the files contain lots of "stuff" that is
>> not meant to be translated. A simple key-value file would be much
>> easier, although in OpenVPN-GUI's case the hardcoded window sizes
>> make this more complex.
>>
>>
>> it makes sense to convert openvpn-gui resources into visual studio format.
>> @selvanair some times ago told something like that.
>>
>
> Hmm, interesting, will need to look into it. Any format that could be
> loaded by a translation memory application is better than what we have now.
> Simple key-value resource files are also easy to convert into other similar
> formats, if necessary.
>
> as for the rest, separate resources are just fine.
>>
>>
>>
>> Also I'm not sure how easy it would be to separate the translatable
>> strings into a separate file. I would guess that the actual .res
>> files could be generated on the fly from a template and the
>> key-value file by the build scripts.
>>
>>
>> it looks overcomplicated. some kind of "post build operation" which will
>> identifies missing language resources would be nice however
>>
>
> Yeah, it could be hairy. Let's look into this in depth later.
>
>
> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
>
> irc freenode net: mattock
>
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Samuli Seppänen]

Hi,

Il 30/11/2016 11:58, Илья Шипицин ha scritto:
>
>
> (and, yes, I'm going to build multi-language installer, probably
> right
> after 2.4 release)
>
>
> This makes sense. Any plans on how you're going to do it?
>
>
>
> as we do not support windows 2000 anymore, we can easily switch to unicode.
> there are few questions
>
> 1) unicode nsis under linux (we use windows+mingw+nsis unicode, so, I'm
> not sure about linux)
>

Unicode seems to be present in Linux NSIS versions, according to this:



The build computers need to be updated to a quite recent NSIS version, 
though.


> 2) split installer into several language files (as done for openvpn-gui)

We'd also need to detect the language the user is using to select the 
correct one. I personally don't like manual language selector as they 
add one more step to the install process.

>
> 3) test everything
>
>
> it is not difficult, but it is time consuming, I'm afraid we will test
> it properly before 2.4

The plan is to release 2.5 pretty quickly after 2.4. Also, installer 
changes do not necessarily need to go in sync with OpenVPN releases.

>
> Another internationalization aspect we could improve is how we store
> translations for OpenVPN-GUI. Editing the resource files directly is
> clumsy and error-prone, as the files contain lots of "stuff" that is
> not meant to be translated. A simple key-value file would be much
> easier, although in OpenVPN-GUI's case the hardcoded window sizes
> make this more complex.
>
>
> it makes sense to convert openvpn-gui resources into visual studio format.
> @selvanair some times ago told something like that.

Hmm, interesting, will need to look into it. Any format that could be 
loaded by a translation memory application is better than what we have 
now. Simple key-value resource files are also easy to convert into other 
similar formats, if necessary.

> as for the rest, separate resources are just fine.
>
>
>
> Also I'm not sure how easy it would be to separate the translatable
> strings into a separate file. I would guess that the actual .res
> files could be generated on the fly from a template and the
> key-value file by the build scripts.
>
>
> it looks overcomplicated. some kind of "post build operation" which will
> identifies missing language resources would be nice however

Yeah, it could be hairy. Let's look into this in depth later.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

--
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Илья Шипицин]

2016-11-30 12:36 GMT+03:00 Samuli Seppänen :

> Il 30/11/2016 09:53, Илья Шипицин ha scritto:
>
>> Hello,
>>
>> as we finished x86 + x64 installer, we can do something else now.
>> @mattock, which installer are you going to build ?
>>
>> it used to be (ndis5, ndis6) x (x86, x64) matrix, what will be future
>> matrix ?
>>
>
> As discussed earlier bloating the (2.4) installers with NDIS5 drivers is
> not worth it. NDIS5 driver is only aimed for Windows XP, and we have
> dropped XP support in OpenVPN 2.4 already. Also, OpenvPN 2.3 will see fewer
> and fewer fixes as 2.4.x releases stabilize. Eventually 2.3 will go into
> "high severity security fixes only"-mode, like 2.2 did several years ago.
>
> So let's not beat the dead horse (NDIS5) anymore :).
>
>
>> (and, yes, I'm going to build multi-language installer, probably right
>> after 2.4 release)
>>
>
> This makes sense. Any plans on how you're going to do it?
>


as we do not support windows 2000 anymore, we can easily switch to unicode.
there are few questions

1) unicode nsis under linux (we use windows+mingw+nsis unicode, so, I'm not
sure about linux)

2) split installer into several language files (as done for openvpn-gui)

3) test everything


it is not difficult, but it is time consuming, I'm afraid we will test it
properly before 2.4



>
> Another internationalization aspect we could improve is how we store
> translations for OpenVPN-GUI. Editing the resource files directly is clumsy
> and error-prone, as the files contain lots of "stuff" that is not meant to
> be translated. A simple key-value file would be much easier, although in
> OpenVPN-GUI's case the hardcoded window sizes make this more complex.
>

it makes sense to convert openvpn-gui resources into visual studio format.
@selvanair some times ago told something like that.

as for the rest, separate resources are just fine.


>
> Also I'm not sure how easy it would be to separate the translatable
> strings into a separate file. I would guess that the actual .res files
> could be generated on the fly from a template and the key-value file by the
> build scripts.
>
>
it looks overcomplicated. some kind of "post build operation" which will
identifies missing language resources would be nice however


> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
>
> irc freenode net: mattock
>
--
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] combined ndis5 + ndis6 installer ?

[Samuli Seppänen]

Il 30/11/2016 09:53, Илья Шипицин ha scritto:
> Hello,
>
> as we finished x86 + x64 installer, we can do something else now.
> @mattock, which installer are you going to build ?
>
> it used to be (ndis5, ndis6) x (x86, x64) matrix, what will be future
> matrix ?

As discussed earlier bloating the (2.4) installers with NDIS5 drivers is 
not worth it. NDIS5 driver is only aimed for Windows XP, and we have 
dropped XP support in OpenVPN 2.4 already. Also, OpenvPN 2.3 will see 
fewer and fewer fixes as 2.4.x releases stabilize. Eventually 2.3 will 
go into "high severity security fixes only"-mode, like 2.2 did several 
years ago.

So let's not beat the dead horse (NDIS5) anymore :).

>
> (and, yes, I'm going to build multi-language installer, probably right
> after 2.4 release)

This makes sense. Any plans on how you're going to do it?

Another internationalization aspect we could improve is how we store 
translations for OpenVPN-GUI. Editing the resource files directly is 
clumsy and error-prone, as the files contain lots of "stuff" that is not 
meant to be translated. A simple key-value file would be much easier, 
although in OpenVPN-GUI's case the hardcoded window sizes make this more 
complex.

Also I'm not sure how easy it would be to separate the translatable 
strings into a separate file. I would guess that the actual .res files 
could be generated on the fly from a template and the key-value file by 
the build scripts.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

--
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

[Openvpn-devel] combined ndis5 + ndis6 installer ?

[Илья Шипицин]

Hello,

as we finished x86 + x64 installer, we can do something else now.
@mattock, which installer are you going to build ?

it used to be (ndis5, ndis6) x (x86, x64) matrix, what will be future
matrix ?

(and, yes, I'm going to build multi-language installer, probably right
after 2.4 release)

Cheers,
Ilya Shipitsin
--
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel