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] package management
Date: Sat, 14 May 2011 17:26:42 +0200	[thread overview]
Message-ID: <20110514172642.3798873a@surf> (raw)
In-Reply-To: <iqm18j$peg$1@dough.gmane.org>

On Sat, 14 May 2011 13:49:07 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:

> > Soon, quite certainly not. Someday, maybe. But there's a lot of
> > work to be done at the package infrastructure level to make this
> > possible. It is not as simple as one might initially think to add
> > this kind of features.
> 
> I'm curious about this.  I'm using ipkg and it works fine.  Opkg seems
> to be based on (and very similar to) ipkg.  What is different about
> opkg that makes it difficult?

Maybe I misunderstood Xianghua initial request. I thought he was asking
for Buildroot to generate ipkg/opkg packages, which Buildroot isn't
capable of doing at the moment. If he is asking about having the
opkg/ipkg-utils installed in a Buildroot system, then obviously it's
fairly easy.

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

  reply	other threads:[~2011-05-14 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-14  2:14 [Buildroot] package management Xianghua Xiao
2011-05-14  9:53 ` Thomas Petazzoni
2011-05-14 13:49   ` Grant Edwards
2011-05-14 15:26     ` Thomas Petazzoni [this message]
2011-05-14 17:35       ` Grant Edwards
2011-05-14 21:31       ` Xianghua Xiao
2011-05-16  4:04         ` Grant Edwards
  -- strict thread matches above, loose matches on Subject: below --
2012-11-27 18:25 [Buildroot] Package Management John Tobias

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=20110514172642.3798873a@surf \
    --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