Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] which ipkg?
Date: Tue, 17 Apr 2007 22:05:01 +0200	[thread overview]
Message-ID: <20070417200501.GA25039@zelow.no> (raw)
In-Reply-To: <20070417150722.GJ23570@aon.at>

On Tue, Apr 17, 2007 at 05:07:22PM +0200, Bernhard Fischer wrote:
> 
> Ideally, we want ipkg in busybox, ultimately.

true enough. I was discusssed a few years ago but nothing happened.

Just checked and the ipkg shell script is 28K and ipkg-cl 2K but it
needs libpkg which is 134K.. 

but libipkg seems to have quite alot of libbb in it but I'm not sure how
much can be shaved off when putting it into busybox.

> I once looked at the
> normal ipkg for a few minutes, and from what i remember, providing
> a nice, working and small applet from it (by rewriting it) looked quite
> reasonable, fwiw.

I may some day try it but not before I need it or someone pays me.

Until then I'll use ipkt-utils (mainly ipkg-build and hopefully not
needing the python part of the utils.) for building the packages and let
the user choose between the shell script and ipkg-cl.

hopefully they are compatible enough. if not I'll do as OpenWRT seems to
have; choose the shell script.

(unless someone here tells me what to do.)



Thomas.

      reply	other threads:[~2007-04-17 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 10:16 [Buildroot] which ipkg? Thomas Lundquist
2007-04-17 11:13 ` Thomas Lundquist
2007-04-17 15:07   ` Bernhard Fischer
2007-04-17 20:05     ` Thomas Lundquist [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=20070417200501.GA25039@zelow.no \
    --to=lists@zelow.no \
    --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