From: Alexey Sokolov <alexey+cygwin@asokolov.org>
To: cygwin-apps@cygwin.com
Subject: [ITP] znc 1.6.0
Date: Sat, 18 Jul 2015 15:48:00 -0000 [thread overview]
Message-ID: <55AA752A.3000303@asokolov.org> (raw)
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?
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?
znc.cygport
------------
NAME="znc"
VERSION=1.6.0
RELEASE=1
HOMEPAGE="http://znc.in/"
SRC_URI="http://znc.in/releases/archive/znc-${VERSION}.tar.gz"
PKG_NAMES="znc znc-devel znc-perl znc-python"
znc_SUMMARY="Advanced IRC bouncer"
znc_DESCRIPTION="ZNC is an IRC network bouncer (BNC). It can detach
the client from the actual IRC server, and also from selected channels.
Multiple clients from different locations can connect to a single ZNC
account
simultaneously and therefore appear under the same nickname on IRC.
It supports SSL secured connections and IPv6."
znc_CONTENTS="usr"
znc_CATEGORY="Net"
znc_devel_SUMMARY="Modules development for ZNC"
znc_devel_DESCRIPTION="This package contains tools to build ZNC modules
written on C++."
znc_devel_CONTENTS="usr/bin/znc-buildmod usr/include usr/lib/pkgconfig"
znc_devel_CATEGORY="Net Devel"
znc_devel_REQUIRES="znc openssl-devel libicu-devel gcc-g++"
znc_perl_SUMMARY="Support for ZNC modules written on Perl"
znc_perl_DESCRIPTION="This package contains Perl bindings for ZNC."
znc_perl_CONTENTS="usr/lib/znc/modperl.so usr/lib/znc/modperl
usr/lib/znc/*.pm"
znc_perl_CATEGORY="Net Perl"
znc_python_SUMMARY="Support for ZNC modules written on Python3"
znc_python_DESCRIPTION="This package contains Python3 bindings for ZNC."
znc_python_CONTENTS="usr/lib/znc/modpython.so usr/lib/znc/modpython"
znc_python_CATEGORY="Net Python"
for exclude in $znc_devel_CONTENTS $znc_perl_CONTENTS
$znc_python_CONTENTS; do
znc_CONTENTS="--exclude=$exclude $znc_CONTENTS"
done
# libcrypt-devel is here only because modperl refuses to compile without it
DEPEND="zlib-devel openssl-devel libcrypt-devel libsasl2-devel
libicu-devel gcc-g++ make pkg-config perl python3"
CYGCONF_ARGS="--enable-zlib --enable-openssl --enable-cyrus
--enable-charset --enable-perl --enable-python"
inherit autotools
--------
znc/setup.hint
------
category: Net
requires: cygwin libgcc1 libicu55 libopenssl100 libsasl2_3 libstdc++6 zlib0
sdesc: "Advanced IRC bouncer"
ldesc: "ZNC is an IRC network bouncer (BNC). It can detach
the client from the actual IRC server, and also from selected channels.
Multiple clients from different locations can connect to a single ZNC
account
simultaneously and therefore appear under the same nickname on IRC.
It supports SSL secured connections and IPv6."
------
znc/znc-devel/setup.hint
------
category: Net Devel
requires: bash znc openssl-devel libicu-devel gcc-g++
sdesc: "Modules development for ZNC"
ldesc: "This package contains tools to build ZNC modules written on C++."
external-source: znc
------
znc/znc-perl/setup.hint
------
category: Net Perl
requires: cygwin libgcc1 libstdc++6 perl_base znc
sdesc: "Support for ZNC modules written on Perl"
ldesc: "This package contains Perl bindings for ZNC."
external-source: znc
-------
znc/znc-python/setup.hint
------
category: Net Python
requires: cygwin libgcc1 libstdc++6 python python3 znc
sdesc: "Support for ZNC modules written on Python3"
ldesc: "This package contains Python3 bindings for ZNC."
external-source: znc
------
znc/znc-debuginfo/setup.hint
-----
category: Debug
requires: cygwin-debuginfo
external-source: znc
sdesc: "Debug info for znc"
ldesc: "This package contains files necessary for debugging the
znc package with gdb."
------
next reply other threads:[~2015-07-18 15:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 15:48 Alexey Sokolov [this message]
[not found] ` <55AABF89.7030306@asokolov.org>
[not found] ` <55AADC2C.1070802@asokolov.org>
2015-07-19 8:24 ` Alexey Sokolov
2015-07-19 10:03 ` Corinna Vinschen
2015-07-19 13:24 ` Alexey Sokolov
2015-07-19 16:42 ` Achim Gratz
[not found] ` <55ABEC90.3040106@asokolov.org>
2015-07-19 18:30 ` Alexey Sokolov
2015-07-19 19:11 ` Achim Gratz
2015-07-19 19:30 ` Marco Atzeri
2015-07-19 19:36 ` Achim Gratz
2015-07-19 19:54 ` Alexey Sokolov
2015-07-20 7:44 ` Corinna Vinschen
2015-07-20 18:58 ` Alexey Sokolov
2015-07-20 20:46 ` Alexey Sokolov
2015-07-21 7:12 ` Corinna Vinschen
2015-07-21 20:37 ` Alexey Sokolov
2015-07-21 23:25 ` David Stacey
2015-07-21 23:32 ` Alexey Sokolov
2015-07-21 23:53 ` Alexey Sokolov
2015-07-22 23:03 ` David Stacey
2015-07-22 23:29 ` David Stacey
2015-07-23 0:58 ` Alexey Sokolov
2015-07-23 5:23 ` Achim Gratz
2015-07-23 20:50 ` Alexey Sokolov
2015-07-23 13:24 ` Ken Brown
2015-07-23 20:50 ` Alexey Sokolov
2015-07-23 21:04 ` Alexey Sokolov
2015-07-23 21:28 ` Ken Brown
2015-07-24 6:42 ` Alexey Sokolov
2015-07-22 8:07 ` Corinna Vinschen
2015-07-22 21:40 ` Alexey Sokolov
2015-07-30 22:34 ` Alexey Sokolov
2015-08-03 7:59 ` Corinna Vinschen
2015-08-03 9:02 ` Alexey Sokolov
2015-08-03 9:20 ` Corinna Vinschen
2015-07-24 19:14 ` Alexey Sokolov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55AA752A.3000303@asokolov.org \
--to=alexey+cygwin@asokolov.org \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).