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 v2 1/2] libsodium: new package
Date: Mon, 18 May 2015 21:53:50 +0200	[thread overview]
Message-ID: <20150518215350.50ff6ca5@free-electrons.com> (raw)
In-Reply-To: <CA+-urNRu=qpsQ_-O_y16-MVoYw-Vxqwc1myZw3mTqV=3aSDiOg@mail.gmail.com>

Dear Frank Hunleth,

On Mon, 18 May 2015 12:07:24 -0400, Frank Hunleth wrote:

> As I said in a previous email, I use the host package and asked for
> guidance for including host packages or not. I didn't see a response.
> While I certainly don't mind removing it, it would be nice to know why
> host packages are such a problem. For me, it is very convenient that
> Buildroot requires so little of the host Linux environment to work.
> Libsodium, in particular, is annoying since you can't apt-get install
> it in Ubuntu 12.04. I know that's old, but it's around. Anyway, that's
> my 2 cents. It will be gone for v3...

The thing is that we generally don't like to have "dangling" packages,
that are not used by anything in Buildroot.

Normally, host packages fall into one of the two following categories:

 * Used as a dependency to build a target package. In this case, the
   host package is listed as host-<foo> in the <pkg>_DEPENDENCIES of
   another package. So it is actually used by something in Buildroot.

 * Used as a tool (for flashing, creating images, debugging, etc.) and
   in this case, it's listed in the "Host utilities" menu in
   menuconfig. In this case, it is directly visible to the user.

But what you propose here does not fall into any of these two cases. We
don't put host libraries in the "Host utilities" menu, and your host
package is not used by any other package in Buildroot, hence Baruch's
reaction.

I think we may have made a couple of exceptions in the past, but I'm
not sure how many. And they still have the major drawback that such
packages will never be tested, because they cannot be reached by
autobuilder testing.

Best regards,

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

  reply	other threads:[~2015-05-18 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 13:19 [Buildroot] [PATCH v2 1/2] libsodium: new package Frank Hunleth
2015-05-18 13:19 ` [Buildroot] [PATCH v2 2/2] zeromq: depend on libsodium if available Frank Hunleth
2015-05-18 15:31 ` [Buildroot] [PATCH v2 1/2] libsodium: new package Baruch Siach
2015-05-18 16:07   ` Frank Hunleth
2015-05-18 19:53     ` Thomas Petazzoni [this message]
2015-05-19 12:05       ` Frank Hunleth

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=20150518215350.50ff6ca5@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