Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Mason <mason+buildroot@postdiluvian.org>
To: buildroot@busybox.net
Subject: [Buildroot] dpkg and apt for buildroot?
Date: Tue, 14 Apr 2015 16:02:22 -0400	[thread overview]
Message-ID: <20150414200222.GB7501@postdiluvian.org> (raw)

Has anyone already done the footwork to add dpkg and apt (at least a
secure apt-get, I'm not sure what other dependancies there are)?

I ran across some mail from July 2013 with patches for dpkg, which
were very close to working, but I didn't see any for apt.  I'm kind of
surprised that apt and friends aren't an option - am I about to run
into something unexpectedly complicated, or is complex package
management like apt/dpkg provides just generally outside of
buildroot's scope?

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?

             reply	other threads:[~2015-04-14 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 20:02 Mark Mason [this message]
2015-04-14 21:09 ` [Buildroot] dpkg and apt for buildroot? Yegor Yefremov
2015-04-20 19:35   ` Mark Mason
2015-04-14 22:34 ` Arnout Vandecappelle

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=20150414200222.GB7501@postdiluvian.org \
    --to=mason+buildroot@postdiluvian.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