Hi,
There is a new upstream version of libunistring: 0.9.4. I have created
the new packages, but I have not uploaded them yet.
In the new version there is a version bump of the dll,
cygunistring-0.dll will be replaced with cygunistring-2.dll. So I expect
that when I upload the new packages,
On 2014-09-21 01:44, Erwin Waterlander wrote:
There is a new upstream version of libunistring: 0.9.4. I have created
the new packages, but I have not uploaded them yet.
In the new version there is a version bump of the dll,
cygunistring-0.dll will be replaced with cygunistring-2.dll. So I
On 21/09/2014 08:44, Erwin Waterlander wrote:
Hi,
There is a new upstream version of libunistring: 0.9.4. I have created
the new packages, but I have not uploaded them yet.
In the new version there is a version bump of the dll,
cygunistring-0.dll will be replaced with cygunistring-2.dll. So I
On 2014-08-17 03:46, Marco Atzeri wrote:
On 17/08/2014 09:56, Yaakov Selkowitz wrote:
On Sun, 2014-08-17 at 09:44 +0200, Marco Atzeri wrote:
On 17/08/2014 08:47, Yaakov Selkowitz wrote:
Why no debuginfo?
no idea.
the build system is a bit basic, pre-autoconf age,
Then you need
I'm not sure what the process is for adopting somebody else's package;
the Submitting a new package instructions don't seem to apply since
it's not a new package, but I don't yet have upload rights to just go
ahead and do it.
Adam, you are now listed as maintainer in cygwin-pkg-maint,
Yaakov Selkowitz schreef op 2014-09-21 09:25:
On 2014-09-21 01:44, Erwin Waterlander wrote:
There is a new upstream version of libunistring: 0.9.4. I have created
the new packages, but I have not uploaded them yet.
In the new version there is a version bump of the dll,
cygunistring-0.dll will
# 32-bit:
BASEURL=https://dl.dropboxusercontent.com/u/119453582/Cygwin/32bit/release
wget --no-check-certificate --no-host-directories --force-directories
--cut-dirs=5 \
${BASEURL}/cppcheck/cppcheck-1.66-1-src.tar.xz \
${BASEURL}/cppcheck/cppcheck-1.66-1.tar.xz \
On 2014-09-21 14:28, David Stacey wrote:
I would like to adopt cppcheck, which was orphaned by Chris Sutcliffe
last week [1]. The following notes may be of use when reviewing this
package:
I have enabled custom rules for cppcheck, which gives the user the scope
to create custom checks. This
