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] buildroot Digest, Vol 71, Issue 9
Date: Wed, 2 May 2012 23:10:27 +0200	[thread overview]
Message-ID: <20120502231027.198c48cc@skate> (raw)
In-Reply-To: <4FA1899E.1050408@essensium.com>

Hello Sitjn,

If you want to contribute to the list, you should consider subscribing
to the list in non-digest mode, because replying to your digest
messages break the discussion threads in the list.

Le Wed, 02 May 2012 21:23:10 +0200,
Stijn Souffriau <stijn.souffriau@essensium.com> a ?crit :

> I can fix all the minor issues, no problem. For me, the only two bigger 
> issues are:
> 
>   - uClibc support: glibc specific headers seemed to be needed in order 
> to build. Maybe I can remedy that but I'm not sure. Can't you ignore 
> this for now so that I or somebody else can add uClibc support later? If 
> it's a problem I'll look into it but my time is limited.

Ok, we can probably do this. In general, the maintainer (Peter
Korsgaard), doesn't like a lot to have glibc-specific packages, but if
you post the patches, maybe others can test and see if the uClibc
compatibility issue is complex or not.

>   - host-gnupg: I needed it to sign file system images (useful for 
> remote upgrades). I'm not sure if buildroot will always build host-gnupg 
> and if this is a problem for you, if so I can always make it optional it 
> with yet another config option.

Ok. But why not using the gnupg provided by the Linux distribution for
this? My vision is that we should generally only add host packages if:

 * Either they are used as build dependencies of target packages;

 * Or they are not easily available in Linux distributions, or are
   really important to have in BSP for development boards (this
   includes tools like AT91 SAM-BA, or openocd)

Of course, such a proposal remains to be discussed, but I don't think
we want to replace what the Linux distribution is doing. Before
reworking your patches about this, please wait for other members of the
Buildroot community to speak up: my opinion is not authoritative.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-05-02 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1335960002.505.buildroot@busybox.net>
2012-05-02 19:23 ` [Buildroot] buildroot Digest, Vol 71, Issue 9 Stijn Souffriau
2012-05-02 21:10   ` Thomas Petazzoni [this message]

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=20120502231027.198c48cc@skate \
    --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