From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] OT: how to do upgrades with ipkg?
Date: Tue, 7 Sep 2010 21:04:20 +0000 (UTC) [thread overview]
Message-ID: <i669ck$glk$1@dough.gmane.org> (raw)
In-Reply-To: 4C86A6D0.7070602@jdines.net
On 2010-09-07, James J. Dines <jdines@jdines.net> wrote:
>
> On 09/07/2010 04:41 PM, Grant Edwards wrote:
>> First, my apologies. This isn't directly related to buildroot, but
>> I'm hoping somebody might know the answer (there doesn't seem to be an
>> ipkg mailing list).
>>
>> When using ipkg to manage field-installed pacakges, how do you upgrade
>> a package? For example, let's say I've got foobar version 0.1
>> installed. Now I have foobar_0.2_arm.ipk at hand on the target. How
>> do I upgrade?
>>
>> The "ipkg upgrade" command doesn't seem relevent -- it won't accept a
>> path to an .ipk file. There are no "feeds" in my system. All packages
>> are explicitly uploaded to the target and installed.
>>
>> Do you just do this?
>>
>> ipkg remove foobar
>> ipkg install foobar_0.2_arm.ipk
Apparently you just "install" the new package. ipkg figures out that
an older version is installed and knows it's upgrading.
> On a related note, wouldn't it make more sense to migrate to opkg at
> this point? http://en.wikipedia.org/wiki/Opkg
Probably.
Development on ipkg seems to have stalled. The newest snapshot
available from handhelds.org is from 2006.
The last commit to the opkg SVN reposity was about two weeks ago.
--
Grant Edwards grant.b.edwards Yow! Uh-oh!! I'm having
at TOO MUCH FUN!!
gmail.com
prev parent reply other threads:[~2010-09-07 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 20:41 [Buildroot] OT: how to do upgrades with ipkg? Grant Edwards
2010-09-07 20:55 ` James J. Dines
2010-09-07 21:04 ` Grant Edwards [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='i669ck$glk$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.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