Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] New package: libyaml
Date: Thu, 14 Jul 2011 19:53:20 +0200	[thread overview]
Message-ID: <87tyaobvfz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1310644607-25251-1-git-send-email-evgeni_dobrev@developer.bg> (Evgeni Dobrev's message of "Thu, 14 Jul 2011 13:56:47 +0200")

>>>>> "Evgeni" == Evgeni Dobrev <evgeni_dobrev@developer.bg> writes:

 Evgeni> YAML 1.1 parser and emitter written in C

Thanks, see below for a few comments..


 Evgeni> ---
 Evgeni>  package/Config.in          |    1 +
 Evgeni>  package/libyaml/Config.in  |    8 ++++++++
 Evgeni>  package/libyaml/libyaml.mk |   14 ++++++++++++++
 Evgeni>  3 files changed, 23 insertions(+), 0 deletions(-)
 Evgeni>  create mode 100644 package/libyaml/Config.in
 Evgeni>  create mode 100644 package/libyaml/libyaml.mk

 Evgeni> diff --git a/package/Config.in b/package/Config.in
 Evgeni> index fb5a570..dee3b70 100644
 Evgeni> --- a/package/Config.in
 Evgeni> +++ b/package/Config.in
 Evgeni> @@ -345,6 +345,7 @@ source "package/libglib2/Config.in"
 Evgeni>  source "package/libnspr/Config.in"
 Evgeni>  source "package/liboil/Config.in"
 Evgeni>  source "package/libsigc/Config.in"
 Evgeni> +source "package/libyaml/Config.in"

I think it would make more sense to put it together with the other
xml/json parsers instead of libraries/other.


 Evgeni>  source "package/startup-notification/Config.in"
 Evgeni>  endmenu
 
 Evgeni> diff --git a/package/libyaml/Config.in b/package/libyaml/Config.in
 Evgeni> new file mode 100644
 Evgeni> index 0000000..23e74a5
 Evgeni> --- /dev/null
 Evgeni> +++ b/package/libyaml/Config.in
 Evgeni> @@ -0,0 +1,8 @@
 Evgeni> +config BR2_PACKAGE_LIBYAML
 Evgeni> +	bool "libyaml"
 Evgeni> +	default n

'n' is default, so you can drop this line.

 Evgeni> +	help
 Evgeni> +	LibYAML is a YAML 1.1 parser and emitter written in C.
 Evgeni> +
 Evgeni> +	http://pyyaml.org/wiki/LibYAML
 Evgeni> +

Help lines are indented with '<tab><space><space>'. You have an extra
empty line at the end that you can also drop.

 Evgeni> diff --git a/package/libyaml/libyaml.mk b/package/libyaml/libyaml.mk
 Evgeni> new file mode 100644
 Evgeni> index 0000000..2e936fc
 Evgeni> --- /dev/null
 Evgeni> +++ b/package/libyaml/libyaml.mk
 Evgeni> @@ -0,0 +1,14 @@
 Evgeni> +#############################################################
 Evgeni> +#
 Evgeni> +# yaml
 Evgeni> +#
 Evgeni> +#############################################################
 Evgeni> +LIBYAML_VERSION = 0.1.4
 Evgeni> +LIBYAML_SOURCE = yaml-$(LIBYAML_VERSION).tar.gz
 Evgeni> +LIBYAML_SITE = http://pyyaml.org/download/libyaml/
 Evgeni> +LIBYAML_INSTALL_STAGING = YES
 Evgeni> +LIBYAML_INSTALL_TARGET = YES

You can drop this line as YES is default.

 Evgeni> +$(eval $(call AUTOTARGETS,package,libyaml))

Otherwise it looks good. Care to fix and resend?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-07-14 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 11:56 [Buildroot] [PATCH] New package: libyaml Evgeni Dobrev
2011-07-14 17:53 ` Peter Korsgaard [this message]
2011-07-14 20:27 ` [Buildroot] [PATCH] XML 1.1 parser and emitter written in C Evgeni Dobrev
2011-07-14 21:26   ` Peter Korsgaard

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=87tyaobvfz.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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