Re: [ITP] znc 1.6.0

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

Hi Alexey,

On Jul 19 09:24, Alexey Sokolov wrote:
> For some reason the mailing list swallows my messages, so I'm trying to
> remove cyrillic letters for "wrote"...
> 
> 19.07.2015 00:07, Alexey Sokolov :
> > 18.07.2015 22:05, Alexey Sokolov :
> >> I've put files in the required directory structure to
> >> http://people.znc.in/~darthgandalf/znc/znc-cygwin/

Packaging looks good, except...

I think libznc.dll should be called libzncX.dll or cygzncX.dll, with X
being a version number.  If there will ever be backward-incompatible
changes in the DLL, the version number should be bumped.  Also, is there
a native Windows version of ZNC?  If so, the name libznc.dll runs danger
of DLL collision.

> >> 18.07.2015 16:47, Alexey Sokolov :
> >>> Hi!
> >>>
> >>> I want to package ZNC.
> >>> Package in distros:
> >>> https://packages.gentoo.org/package/net-irc/znc
> >>> https://packages.debian.org/search?keywords=znc
> >>> http://packages.ubuntu.com/search?keywords=znc
> >>> https://admin.fedoraproject.org/pkgdb/package/znc/
> >>>
> >>> Also I have several questions:
> >>> 1) cygport chose to make znc-python to depend on both python and
> >>> python3, though I want it to depend only on python3. Is there some way
> >>> to force not to depend on python?
> > The answer to this is "inherit python3" (thanks jturney)
> >
> >
> >>> 2) I can setup CI, so that on every push to git master new package is
> >>> pushed, marked as "test". Is it a good idea or not?

I would only do that for selected new versions, not for every push.

For uploading, please send the ssh key per
https://sourceware.org/cygwin-apps/package-upload.html


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]