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 12:16:31 +0200	[thread overview]
Message-ID: <20070417101631.GA12039@zelow.no> (raw)


Hi.


I am preparing a patch for building autonomous packages in buildroot and
I have tarballs and "udebs" but I also want ipkg.

The big question is; which ipkg version should I/we go for?
handhelds.org has at least two options, the original shell script based
(ipkg-utils) or a C-based newer one.

The C-based seems to be handheld.orgs preferred but the TODO in the
snapshot source mentions "unstable" and it does not have a binary named "ipkg",
just "ipkg-cl" which makes me something between curious and worried.

The CVS repo has some newer code but no snapshots.

anyone familiar with ipkg that has a suggestion on what I should pick?

(or both, chooseable?)


Thomas.

             reply	other threads:[~2007-04-17 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 10:16 Thomas Lundquist [this message]
2007-04-17 11:13 ` [Buildroot] which ipkg? Thomas Lundquist
2007-04-17 15:07   ` Bernhard Fischer
2007-04-17 20:05     ` Thomas Lundquist

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=20070417101631.GA12039@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