From: James J. Dines <jdines@jdines.net>
To: buildroot@busybox.net
Subject: [Buildroot] OT: how to do upgrades with ipkg?
Date: Tue, 07 Sep 2010 16:55:44 -0400 [thread overview]
Message-ID: <4C86A6D0.7070602@jdines.net> (raw)
In-Reply-To: <i6680v$ahj$1@dough.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
>
On a related note, wouldn't it make more sense to migrate to opkg at
this point? http://en.wikipedia.org/wiki/Opkg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMhqbNAAoJECSpOhdQESq66rkH/0TclZj56eKEkoZJFA1XSh37
4nTt4yXMZOjDjMwtKYwOee3G04qJnx4dboNEyz4Z1oL6YPEEE+ROIBi5pTzni4oD
AA+b+erNmVSnNr1riKoQ7QTaxbbiijaSXPOshvp0FlXJ7HcS92tnahGdYpAuXfza
wYWO82ACjlafotWEZ3ZeP2jxIiAIkz5aQ5ESjqlLXQyWCgmt5RxE0O1Wf3ujjPEs
KufiQFLf0Tnt311ADLXfaub3ucsdnrRh1g6YRpXELXQpX7raR1gVCy2RMNRJOeFv
q+3H88dQ1Bvp+YKtK3CeOiCsUfUh7PA0/rCml1WA772nr/VPQCxbUZ6QcBAq7+U=
=45ID
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-09-07 20:55 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 [this message]
2010-09-07 21:04 ` Grant Edwards
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=4C86A6D0.7070602@jdines.net \
--to=jdines@jdines.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.