Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] dpkg and apt for buildroot?
Date: Wed, 15 Apr 2015 00:34:55 +0200	[thread overview]
Message-ID: <552D960F.7050603@mind.be> (raw)
In-Reply-To: <20150414200222.GB7501@postdiluvian.org>

On 14/04/15 22:02, Mark Mason wrote:
> While I'm at it, almost all of the traffic on this list is related to
> development of buildroot rather than development with buildroot.  Is
> there a better place for questions (after the documentation and web
> searches have not provided answers), or is this it?

 This is it. Development with buildroot pretty quickly winds down to development
of buildroot, since you'll often have to add some package - not so much because
buildroot doesn't have enough packages, but rather because it is used in pretty
specific circumstances that require adding specific packages.

 We have considered splitting the list into a buildroot-devel and
buildroot-users, but the buildroot-users list would be almost empty, and the
devel subjects (i.e. new packages being added) are often also relevant for users.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      parent reply	other threads:[~2015-04-14 22:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 20:02 [Buildroot] dpkg and apt for buildroot? Mark Mason
2015-04-14 21:09 ` Yegor Yefremov
2015-04-20 19:35   ` Mark Mason
2015-04-14 22:34 ` Arnout Vandecappelle [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=552D960F.7050603@mind.be \
    --to=arnout@mind.be \
    --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