Re: gnupg2 ?

2017-06-29 Thread Marco Atzeri

On 29/06/2017 08:27, Yaakov Selkowitz wrote:

Marco,

In order to update gpgme, we need libassuan in the distribution, as
GnuPG 2 support is no longer optional.  While I think we could get by
with just that (and allow it to fall back to 1.x support at runtime), it
did spur me to take another look at the gnupg2 stack.  I don't know if
it's *perfect* but it seems to be generally working:

https://github.com/cygwinports/libassuan
https://github.com/cygwinports/libksba
https://github.com/cygwinports/npth
https://github.com/cygwinports/gnupg2
https://github.com/cygwinports/pinentry
https://github.com/cygwinports/gpa

Any chance you could test this out and/or be interested in maintaining
some or all of it?



I am uploading all except gpa, that will follow later.

Thanks
Marco


Re: Perl 5.26

2017-06-29 Thread Achim Gratz
Ken Brown writes:
> Could you send me your cygport file and patches for perl-5.26.0?  Or
> just make it available for download?  I'd like to begin testing it for
> my own purposes.

Sent to you as PM.

Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds


Re: ITA nasm

2017-06-29 Thread Achim Gratz
Doug Henderson writes:
> I'm not sure why the current versions are at
> different numbers, unless an upgrade was requested for 64 bit only.

As Chong Yidong used to say: "Hysterical raisins".  My guess is that
only the x86 version was from the original maintainer and the x68_64
version was actually provided by Yaakov.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs


Re: ITA nasm

2017-06-29 Thread Marco Atzeri

On 29/06/2017 19:29, Doug Henderson wrote:

On 29 June 2017 at 09:38, Marco Atzeri  wrote:

On 29/06/2017 17:22, Doug Henderson wrote:


I am willing to take over maintenance of the nasm package.





Source and download:
# source and patch files
HOMEPAGE="http://www.nasm.us/";
SRC_URI="http://www.nasm.us/pub/nasm/releasebuilds/${PV}/${P}.tar.xz";

I have changed initial release number to 1


can share your build somewhere in the Web ?
It will make easy to cross check for any of us.


I will keep both 32 bit and 64 bit versions at the same version to the
extent possible. I'm not sure why the current versions are at
different numbers, unless an upgrade was requested for 64 bit only.


I bet the 64 version was upload by another maintainer,
not the official one, when we populated the 64 distribution.


Doug



Re: ITA nasm

2017-06-29 Thread Doug Henderson
On 29 June 2017 at 09:38, Marco Atzeri  wrote:
> On 29/06/2017 17:22, Doug Henderson wrote:
>>
>> I am willing to take over maintenance of the nasm package.
>>
>> Info for current release:
>>
>> # package name
>> NAME="nasm"
>> VERSION=2.10.07
>> RELEASE=2
>
>
> are you planning to just align the x86 and x86_64 version ?
> It is worth ?
>
>>
>> # .hint generation
>> CATEGORY="Devel"
>> SUMMARY="The Netwide Assembler"
>> DESCRIPTION="NASM is a widespread, portable, very flexible and mature
>> assembler tool with support for many output formats licensed under the
>> 2-clause BSD licence."
>
>
> it  misses the info about where to download the source
>
>> I plan to package 2.13.01-0 based on the latest upstream release.
>
>
> better 2.13.01-1 as we are using "-0.x" for test pre-release when needed
>

Source and download:
# source and patch files
HOMEPAGE="http://www.nasm.us/";
SRC_URI="http://www.nasm.us/pub/nasm/releasebuilds/${PV}/${P}.tar.xz";

I have changed initial release number to 1

I will keep both 32 bit and 64 bit versions at the same version to the
extent possible. I'm not sure why the current versions are at
different numbers, unless an upgrade was requested for 64 bit only.

Doug

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com


Re: ITA nasm

2017-06-29 Thread Marco Atzeri

On 29/06/2017 17:22, Doug Henderson wrote:

I am willing to take over maintenance of the nasm package.

Info for current release:

# package name
NAME="nasm"
VERSION=2.10.07
RELEASE=2


are you planning to just align the x86 and x86_64 version ?
It is worth ?



# .hint generation
CATEGORY="Devel"
SUMMARY="The Netwide Assembler"
DESCRIPTION="NASM is a widespread, portable, very flexible and mature
assembler tool with support for many output formats licensed under the
2-clause BSD licence."


it  misses the info about where to download the source


I plan to package 2.13.01-0 based on the latest upstream release.


better 2.13.01-1 as we are using "-0.x" for test pre-release when needed


Doug


Regards
Marco


ITA nasm

2017-06-29 Thread Doug Henderson
I am willing to take over maintenance of the nasm package.

Info for current release:

# package name
NAME="nasm"
VERSION=2.10.07
RELEASE=2

# .hint generation
CATEGORY="Devel"
SUMMARY="The Netwide Assembler"
DESCRIPTION="NASM is a widespread, portable, very flexible and mature
assembler tool with support for many output formats licensed under the
2-clause BSD licence."

I plan to package 2.13.01-0 based on the latest upstream release.

Doug

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com


Re: gnupg2 ?

2017-06-29 Thread Marco Atzeri

On 29/06/2017 08:27, Yaakov Selkowitz wrote:

Marco,

In order to update gpgme, we need libassuan in the distribution, as
GnuPG 2 support is no longer optional.  While I think we could get by
with just that (and allow it to fall back to 1.x support at runtime), it
did spur me to take another look at the gnupg2 stack.  I don't know if
it's *perfect* but it seems to be generally working:

https://github.com/cygwinports/libassuan
https://github.com/cygwinports/libksba
https://github.com/cygwinports/npth
https://github.com/cygwinports/gnupg2
https://github.com/cygwinports/pinentry
https://github.com/cygwinports/gpa

Any chance you could test this out and/or be interested in maintaining
some or all of it?



Hi Yaakov,

on my tests on 64 bit libassuan was always failing.
I looked inside the code and I saw a lot of
assumption on cygwin that seems not anymore, if ever, valid.

I will look on your proposal

Regards
Marco