Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] dpkg and apt for buildroot?
@ 2015-04-14 20:02 Mark Mason
  2015-04-14 21:09 ` Yegor Yefremov
  2015-04-14 22:34 ` Arnout Vandecappelle
  0 siblings, 2 replies; 4+ messages in thread
From: Mark Mason @ 2015-04-14 20:02 UTC (permalink / raw)
  To: buildroot

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?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] dpkg and apt for buildroot?
  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
  1 sibling, 1 reply; 4+ messages in thread
From: Yegor Yefremov @ 2015-04-14 21:09 UTC (permalink / raw)
  To: buildroot

Dear Mark,

On Tue, Apr 14, 2015 at 10:02 PM, Mark Mason
<mason+buildroot@postdiluvian.org> wrote:
> 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?

Have you read this section?
http://nightly.buildroot.org/manual.html#faq-no-binary-packages

Yegor

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] dpkg and apt for buildroot?
  2015-04-14 20:02 [Buildroot] dpkg and apt for buildroot? Mark Mason
  2015-04-14 21:09 ` Yegor Yefremov
@ 2015-04-14 22:34 ` Arnout Vandecappelle
  1 sibling, 0 replies; 4+ messages in thread
From: Arnout Vandecappelle @ 2015-04-14 22:34 UTC (permalink / raw)
  To: buildroot

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] dpkg and apt for buildroot?
  2015-04-14 21:09 ` Yegor Yefremov
@ 2015-04-20 19:35   ` Mark Mason
  0 siblings, 0 replies; 4+ messages in thread
From: Mark Mason @ 2015-04-20 19:35 UTC (permalink / raw)
  To: buildroot

Yegor Yefremov <yegorslists@googlemail.com> wrote:

> Dear Mark,
> 
> On Tue, Apr 14, 2015 at 10:02 PM, Mark Mason
> <mason+buildroot@postdiluvian.org> wrote:
> > 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?
> 
> Have you read this section?
> http://nightly.buildroot.org/manual.html#faq-no-binary-packages

Sorry for the delays, I've been working on other stuff, just got back
to the packages.

I did read that section, but I'm not looking for packages of
buildroot, I just need apt to maintain software that's not part of
buildroot.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-04-20 19:35 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox