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
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]>+
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
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/;
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
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
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
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
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
