Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added keepalived package
Date: Tue, 7 Feb 2017 17:46:27 +0100	[thread overview]
Message-ID: <20170207174627.025008a8@free-electrons.com> (raw)
In-Reply-To: <1486484458-8233-2-git-send-email-apalos@gmail.com>

Hello,

On Tue,  7 Feb 2017 18:20:58 +0200, Ilias Apalodimas wrote:
> Signed-off-by: Ilias Apalodimas <apalos@gmail.com>

Thanks for this patch. This looks mostly good, so great for a first
contribution.

A few comments:

 - You don't need to send a series with a cover letter for just a
   single patch. Just send the patch itself.

 - Make a change to the DEVELOPERS file to associate your name/email to
   this package. This way, you'll get notified when/if this package
   fails to build, or when someone sends a patch touching this package.

 - You're missing a hash file. See other packages and the manual for
   the format/details.

> diff --git a/package/keepalived/Config.in b/package/keepalived/Config.in
> new file mode 100644
> index 0000000..ee4ab7a
> --- /dev/null
> +++ b/package/keepalived/Config.in
> @@ -0,0 +1,13 @@
> +config BR2_PACKAGE_KEEPALIVED
> +	bool "keepalived"
> +	select BR2_PACKAGE_OPENSSL
> +	select BR2_PACKAGE_POPT

Are you sure this builds even for no-MMU platforms, static linking
scenario? It's pretty likely that keepalived uses fork() and therefore
will not work on no-MMU platforms.

Yann E. Morin has just submitted a script today to help checking a
package, you may want to use it. It will be merged soon, which will
make things easier.

Thanks!

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

  reply	other threads:[~2017-02-07 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 16:20 [Buildroot] [PATCH 0/1] Added keepalived package Ilias Apalodimas
2017-02-07 16:20 ` [Buildroot] [PATCH 1/1] " Ilias Apalodimas
2017-02-07 16:46   ` Thomas Petazzoni [this message]
2017-02-07 16:57     ` Ilias Apalodimas

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=20170207174627.025008a8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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