From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] move to opkg
Date: Tue, 18 Mar 2008 18:05:35 +0100 [thread overview]
Message-ID: <frosov$c0b$1@ger.gmane.org> (raw)
In-Reply-To: <1205858910.7500.39.camel@dax.rpnet.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
| On Tue, 2008-03-18 at 15:32 +0100, Koen Kooi wrote:
|> Geoffrey Wossum schreef:
|> | I understand that opkg is a fork of ipkg, since ipkg was unmaintained.
|> But
|> | could someone explain what, if anything, this means to me as someone
|> | currently building a product using OpenEmbedded for the underpinning?
|>
|> It means that after this gets applied you login to your product:
|>
|> ssh user@mytarget
|> $ su -
|> Password:
|> # ipkg update
|> sh: ipkg: : command not found
|> # opkg update
|> <output of opkg downloading stuff from feeds>
|>
|> So from a device user POV you need to type 'opkg' instead of 'ipkg'.
|> ~From a developer POV you gain PGP signed packages.
|
| That isn't the full story since the config files moved
| from /usr/lib/ipkg to /usr/lib/opkg and distro maintainers need to be
| wary of the transition. I think Angstrom has something to help with this
| but I'm not sure?
There is opkg-ipkg-compat.bb and angstrom-feed-configs.bb to help with a
dual system, and opkg-r10.patch moves angstrom over to opkg completely.
| While I think about this, would now be a good time to move the config
| files to /var instead of /usr?
I have no strong opinion on that.
regards,
Koen
| Poky can't do that yet since we don't have the var changes in OE but I
| think most of /var in OE is persistent now?
|
| Cheers,
|
| Richard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD4DBQFH3/ZfMkyGM64RGpERAp/pAKCBr14wI9/P6z9tc38Xa2w/dIXZZQCXUx6i
L5hGyxpIf+jsTbuI54y8MA==
=eF5Z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-18 17:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 8:55 [RFC] move to opkg Koen Kooi
2008-03-18 9:55 ` Junqian Gordon Xu
2008-03-19 15:33 ` WPkg Silvano Catinella
2008-03-25 17:23 ` WPkg Michael 'Mickey' Lauer
2008-03-25 23:42 ` WPkg Rod Whitby
2008-04-01 9:15 ` WPkg Silvano Catinella
2008-03-18 9:56 ` [RFC] move to opkg Marcin Juszkiewicz
2008-03-18 10:09 ` Koen Kooi
2008-03-18 10:42 ` Koen Kooi
2008-03-18 11:34 ` Jacob Thebault-Spieker
2008-03-18 11:42 ` Koen Kooi
2008-03-18 13:49 ` Geoffrey Wossum
2008-03-18 14:32 ` Koen Kooi
2008-03-18 16:48 ` Richard Purdie
2008-03-18 17:05 ` Koen Kooi [this message]
2008-03-23 0:38 ` Mike (mwester)
2008-03-23 5:17 ` Mike (mwester)
2008-03-23 10:43 ` Marcin Juszkiewicz
2008-03-23 11:02 ` Koen Kooi
2008-03-23 13:25 ` Mike (mwester)
2008-03-23 18:18 ` Tom Rini
2008-03-23 18:55 ` Koen Kooi
2008-03-23 22:20 ` Tom Rini
2008-03-23 23:10 ` Rod Whitby
2008-03-23 23:06 ` Richard Purdie
2008-03-23 23:46 ` Rod Whitby
2008-03-24 4:30 ` Mike (mwester)
2008-03-24 7:55 ` Stelios Koroneos
2008-03-18 18:12 ` Tom Rini
2008-03-18 18:18 ` Mikhail Gusarov
2008-03-18 18:40 ` Koen Kooi
2008-03-19 9:06 ` Richard Purdie
2008-03-19 9:13 ` Marcin Juszkiewicz
2008-03-18 14:35 ` Marcin Juszkiewicz
2008-03-18 22:00 ` Koen Kooi
2008-03-19 17:52 ` [RFC] move to opkg / md5 error on big-endian machine Jeremy Lainé
2008-03-22 20:38 ` Jeremy Lainé
2008-03-23 10:59 ` [RFC] move to opkg Jeremy Lainé
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='frosov$c0b$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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