[Buildroot] [PATCH] ZNC: new package

[Buildroot] [PATCH] ZNC: new package

[Cédric Chépied]

ZNC is an IRC bouncer.
It is available in menu "Networking applications"
---
 package/Config.in     |  1 +
 package/znc/Config.in |  6 ++++++
 package/znc/znc.mk    | 22 ++++++++++++++++++++++
 3 files changed, 29 insertions(+)
 create mode 100644 package/znc/Config.in
 create mode 100644 package/znc/znc.mk

diff --git a/package/Config.in b/package/Config.in
index 35de506..925a6bf 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -936,6 +936,7 @@ source "package/wpa_supplicant/Config.in"
 source "package/wvdial/Config.in"
 source "package/xinetd/Config.in"
 source "package/xl2tp/Config.in"
+source "package/znc/Config.in"
 
 endmenu
 
diff --git a/package/znc/Config.in b/package/znc/Config.in
new file mode 100644
index 0000000..ef5db26
--- /dev/null
+++ b/package/znc/Config.in
@@ -0,0 +1,6 @@
+config BR2_PACKAGE_ZNC
+       bool "znc"
+       select BR2_PACKAGE_OPENSSL
+       select BR2_PACKAGE_PERL
+       help
+         Advanced IRC bouncer
diff --git a/package/znc/znc.mk b/package/znc/znc.mk
new file mode 100644
index 0000000..59d10f2
--- /dev/null
+++ b/package/znc/znc.mk
@@ -0,0 +1,22 @@
+ZNC_VERSION = 1.2
+ZNC_SOURCE = znc-$(ZNC_VERSION).tar.gz
+ZNC_SITE = http://znc.in/releases
+ACL_INSTALL_STAGING = YES
+
+# While the configuration system uses autoconf, the Makefiles are
+# hand-written and do not use automake. Therefore, we have to hack
+# around their deficiencies by passing installation paths.
+ACL_INSTALL_STAGING_OPT = 			\
+	prefix=$(STAGING_DIR)/usr 		\
+	exec_prefix=$(STAGING_DIR)/usr 		\
+	PKG_DEVLIB_DIR=$(STAGING_DIR)/usr/lib	\
+	install-dev install-lib
+
+ACL_INSTALL_TARGET_OPT = 			\
+	prefix=$(TARGET_DIR)/usr 		\
+	exec_prefix=$(TARGET_DIR)/usr 		\
+	install install-lib
+
+
+$(eval $(autotools-package))
+
-- 
1.8.5.2

[Buildroot] [PATCH] ZNC: new package

[Peter Korsgaard]

>>>>> "C?dric" == C?dric Ch?pied <cedric.chepied@gmail.com> writes:

 > ZNC is an IRC bouncer.
 > It is available in menu "Networking applications"
 > ---
 >  package/Config.in     |  1 +
 >  package/znc/Config.in |  6 ++++++
 >  package/znc/znc.mk    | 22 ++++++++++++++++++++++
 >  3 files changed, 29 insertions(+)
 >  create mode 100644 package/znc/Config.in
 >  create mode 100644 package/znc/znc.mk

 > diff --git a/package/Config.in b/package/Config.in
 > index 35de506..925a6bf 100644
 > --- a/package/Config.in
 > +++ b/package/Config.in
 > @@ -936,6 +936,7 @@ source "package/wpa_supplicant/Config.in"
 >  source "package/wvdial/Config.in"
 >  source "package/xinetd/Config.in"
 >  source "package/xl2tp/Config.in"
 > +source "package/znc/Config.in"
 
 >  endmenu
 
 > diff --git a/package/znc/Config.in b/package/znc/Config.in
 > new file mode 100644
 > index 0000000..ef5db26
 > --- /dev/null
 > +++ b/package/znc/Config.in
 > @@ -0,0 +1,6 @@
 > +config BR2_PACKAGE_ZNC
 > +       bool "znc"
 > +       select BR2_PACKAGE_OPENSSL
 > +       select BR2_PACKAGE_PERL
 > +       help
 > +         Advanced IRC bouncer
 > diff --git a/package/znc/znc.mk b/package/znc/znc.mk
 > new file mode 100644
 > index 0000000..59d10f2
 > --- /dev/null
 > +++ b/package/znc/znc.mk
 > @@ -0,0 +1,22 @@
 > +ZNC_VERSION = 1.2
 > +ZNC_SOURCE = znc-$(ZNC_VERSION).tar.gz
 > +ZNC_SITE = http://znc.in/releases
 > +ACL_INSTALL_STAGING = YES

Why does it need to install into staging? It's a program and not a
library, right?


 > +
 > +# While the configuration system uses autoconf, the Makefiles are
 > +# hand-written and do not use automake. Therefore, we have to hack
 > +# around their deficiencies by passing installation paths.
 > +ACL_INSTALL_STAGING_OPT = 			\
 > +	prefix=$(STAGING_DIR)/usr 		\
 > +	exec_prefix=$(STAGING_DIR)/usr 		\
 > +	PKG_DEVLIB_DIR=$(STAGING_DIR)/usr/lib	\
 > +	install-dev install-lib
 > +
 > +ACL_INSTALL_TARGET_OPT = 			\
 > +	prefix=$(TARGET_DIR)/usr 		\
 > +	exec_prefix=$(TARGET_DIR)/usr 		\
 > +	install install-lib

Out of interest, what does PKG_DEVLIB_DIR do and why don't we pass it
for TARGET?

-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] ZNC: new package

[Cédric Chépied]

At Sun, 05 Jan 2014 11:07:47 +0100,
Peter Korsgaard wrote:
> 
> >>>>> "C?dric" == C?dric Ch?pied <cedric.chepied@gmail.com> writes:
>  > diff --git a/package/znc/znc.mk b/package/znc/znc.mk
>  > new file mode 100644
>  > index 0000000..59d10f2
>  > --- /dev/null
>  > +++ b/package/znc/znc.mk
>  > @@ -0,0 +1,22 @@
>  > +ZNC_VERSION = 1.2
>  > +ZNC_SOURCE = znc-$(ZNC_VERSION).tar.gz
>  > +ZNC_SITE = http://znc.in/releases
>  > +ACL_INSTALL_STAGING = YES
> 
> Why does it need to install into staging? It's a program and not a
> library, right?

It does not. This is a bad copy/paste. I made this patch too quickly. 

> 
> 
>  > +
>  > +# While the configuration system uses autoconf, the Makefiles are
>  > +# hand-written and do not use automake. Therefore, we have to hack
>  > +# around their deficiencies by passing installation paths.
>  > +ACL_INSTALL_STAGING_OPT = 			\
>  > +	prefix=$(STAGING_DIR)/usr 		\
>  > +	exec_prefix=$(STAGING_DIR)/usr 		\
>  > +	PKG_DEVLIB_DIR=$(STAGING_DIR)/usr/lib	\
>  > +	install-dev install-lib
>  > +
>  > +ACL_INSTALL_TARGET_OPT = 			\
>  > +	prefix=$(TARGET_DIR)/usr 		\
>  > +	exec_prefix=$(TARGET_DIR)/usr 		\
>  > +	install install-lib
> 
> Out of interest, what does PKG_DEVLIB_DIR do and why don't we pass it
> for TARGET?


Same remark, I'll fix it and submit a new patch.

Regards,

-- 
C?dric Ch?pied
<cedric.chepied@gmail.com>

[Buildroot] [PATCH] ZNC: new package

[Thomas Petazzoni]

Dear C?dric Ch?pied,

On Sun, 05 Jan 2014 12:57:20 +0100, C?dric Ch?pied wrote:

> > Out of interest, what does PKG_DEVLIB_DIR do and why don't we pass it
> > for TARGET?
> 
> Same remark, I'll fix it and submit a new patch.

Do you plan on resending an updated version of your ZNC package? You
received some comments on January 5th, but we haven't received a new
version.

This new package would be an appreciated contribution, but if you want
to see it accepted, you should resend regularly new versions that take
into account the review comments made by the other Buildroot developers.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH] ZNC: new package

[Thomas Petazzoni]

Dear C?dric Ch?pied,

On Sat,  4 Jan 2014 23:59:30 +0100, C?dric Ch?pied wrote:
> ZNC is an IRC bouncer.
> It is available in menu "Networking applications"
> ---
>  package/Config.in     |  1 +
>  package/znc/Config.in |  6 ++++++
>  package/znc/znc.mk    | 22 ++++++++++++++++++++++
>  3 files changed, 29 insertions(+)
>  create mode 100644 package/znc/Config.in
>  create mode 100644 package/znc/znc.mk
> 
> diff --git a/package/Config.in b/package/Config.in
> index 35de506..925a6bf 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -936,6 +936,7 @@ source "package/wpa_supplicant/Config.in"
>  source "package/wvdial/Config.in"
>  source "package/xinetd/Config.in"
>  source "package/xl2tp/Config.in"
> +source "package/znc/Config.in"
>  
>  endmenu
>  
> diff --git a/package/znc/Config.in b/package/znc/Config.in
> new file mode 100644
> index 0000000..ef5db26
> --- /dev/null
> +++ b/package/znc/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_ZNC
> +       bool "znc"
> +       select BR2_PACKAGE_OPENSSL
> +       select BR2_PACKAGE_PERL
> +       help
> +         Advanced IRC bouncer

We generally want the URL of the project here in the help text. See
what we do for all other packages.

Looking at the configure.ac from ZNC, it seems like the OpenSSL and
Perl support is optional, and can be disabled using --disable-openssl
and --disable-perl. It would probably be a good idea to use these to
make these dependencies optional.

Also, your znc.mk should have ZNC_LICENSE and ZNC_LICENSE_FILES
defined. Look at the Buildroot manual for details about these.

Thanks for your contribution!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH] ZNC: new package

[Cédric Chépied]

Dear Thomas,

At Tue, 28 Jan 2014 19:52:59 +0100,
Thomas Petazzoni wrote:
> Looking at the configure.ac from ZNC, it seems like the OpenSSL and
> Perl support is optional, and can be disabled using --disable-openssl
> and --disable-perl. It would probably be a good idea to use these to
> make these dependencies optional.

When I try to enable perl, configure fails. It uses the perl executable to
generate LDFLAGS but it does that with "my" executable (/usr/bin/perl) and then
tries to link with /usr/lib/perl5/core_perl/CORE/libperl.so which of course
fails.

For python, configure programs can use ./output/host/usr/bin/python2.7 but I
can't find the same for perl. I only find perl compiled for my target.

How can I fix this?

Regards,
-- 
C?dric Ch?pied
<cedric.chepied@gmail.com>

[Buildroot] [PATCH] ZNC: new package

[Cédric Chépied]

A non-text attachment was scrubbed...
Name: 0001-ZNC-new-package.patch
Type: application/octet-stream
Size: 1992 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140101/98bd1c88/attachment.obj>

[Buildroot] [PATCH] ZNC: new package

[Thomas Petazzoni]

Dear C?dric Ch?pied,

Thanks for your patch, but you sent it as an attached file, which is
not very practical for reviewing patches. Please send it inline inside
the e-mail. To do this properly without interferences from your e-mail
client, I strongly recommend you to use "git send-email" to send your
patches.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH] ZNC: new package

[Thomas Petazzoni]

Dear C?dric Ch?pied,

On Thu, 02 Jan 2014 11:42:52 +0100, C?dric Ch?pied wrote:
> Dear Thomas,
> 
> At Thu, 2 Jan 2014 09:59:01 +0100,
> Thomas Petazzoni wrote:
> > Thanks for your patch, but you sent it as an attached file, which is
> > not very practical for reviewing patches. Please send it inline inside
> > the e-mail.
> 
> Do I need to resend it with git send-email or is it ok for this time?

Yes, please resend it with git send-email so that we can review the
patch. Also, please keep the Buildroot mailing list in Cc when
following up on a Buildroot discussion.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH] ZNC: new package

[Jeremy Rosen]

Cedric,

FYI I wrote a small "howto contribute to buildroot" here http://www.linuxembedded.fr/2013/03/votre-premiere-contribution-a-buildroot/

it includes a handy checklist of all the stuff you need to check before posting a patch and it also details the git-send-email command to use...

hopefully this will save you some time...


Cordialement 

J?r?my Rosen 
+33 (0)1 42 68 28 04

fight key loggers : write some perl using vim 


Open Wide Ingenierie

23, rue Daviel
75012 Paris - France
www.openwide.fr





----- Mail original -----
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot