handbook: Update to reference opkg. not ipkg
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@4744 311d38ba-8fff-0310-9ca6-ca027cbcb966
This commit is contained in:
parent
8e9f535de8
commit
d5d1466025
|
@ -532,18 +532,18 @@ $ bitbake matchbox-desktop -c devshell
|
|||
Firstly you want to install the <emphasis>foo</emphasis> package to tmp/rootfs
|
||||
by doing:
|
||||
</para>
|
||||
<programlisting>tmp/staging/i686-linux/usr/bin/ipkg-cl -f \
|
||||
tmp/work/<target-abi>/poky-image-sato-1.0-r0/temp/ipkg.conf -o \
|
||||
<programlisting>tmp/staging/i686-linux/usr/bin/opkg-cl -f \
|
||||
tmp/work/<target-abi>/poky-image-sato-1.0-r0/temp/opkg.conf -o \
|
||||
tmp/rootfs/ update</programlisting>
|
||||
<para>
|
||||
then,
|
||||
</para>
|
||||
<programlisting>tmp/staging/i686-linux/usr/bin/ipkg-cl -f \
|
||||
tmp/work/<target-abi>/poky-image-sato-1.0-r0/temp/ipkg.conf \
|
||||
<programlisting>tmp/staging/i686-linux/usr/bin/opkg-cl -f \
|
||||
tmp/work/<target-abi>/poky-image-sato-1.0-r0/temp/opkg.conf \
|
||||
-o tmp/rootfs install foo
|
||||
|
||||
tmp/staging/i686-linux/usr/bin/ipkg-cl -f \
|
||||
tmp/work/<target-abi>/poky-image-sato-1.0-r0/temp/ipkg.conf \
|
||||
tmp/staging/i686-linux/usr/bin/opkg-cl -f \
|
||||
tmp/work/<target-abi>/poky-image-sato-1.0-r0/temp/opkg.conf \
|
||||
-o tmp/rootfs install foo-dbg</programlisting>
|
||||
<para>
|
||||
which installs the debugging information too.
|
||||
|
@ -802,7 +802,7 @@ $ opreport -cl
|
|||
located in /boot/vmlinux-KERNELVERSION, where KERNEL-version is the version of
|
||||
the kernel e.g. 2.6.23. Poky generates separate vmlinux packages for each kernel
|
||||
it builds so it should be a question of just ensuring a matching package is
|
||||
installed (<command> ipkg install kernel-vmlinux</command>. These are automatically
|
||||
installed (<command> opkg install kernel-vmlinux</command>. These are automatically
|
||||
installed into development and profiling images alongside OProfile. There is a
|
||||
configuration option within the OProfileUI settings page where the location of
|
||||
the vmlinux file can be entered.
|
||||
|
|
|
@ -618,7 +618,7 @@ BBFILE_PRIORITY_extras = "5"</literallayout>
|
|||
the repository and don't have to remember to rebuild any sections.
|
||||
The second is to ensure that target users are able to upgrade their
|
||||
devices via their package manager such as with the <command>
|
||||
ipkg update;ipkg upgrade</command> commands (or similar for
|
||||
opkg update;opkg upgrade</command> commands (or similar for
|
||||
dpkg/apt or rpm based systems). The aim is to ensure Poky has
|
||||
upgradable packages in all cases.
|
||||
</para>
|
||||
|
|
|
@ -119,7 +119,7 @@
|
|||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Poky can build packages in various formats, ipkg, Debian package, or RPM. The package can then be upgraded using the package tools on the device, much like on a desktop distribution like Ubuntu or Fedora.
|
||||
Poky can build packages in various formats, ipk (for ipkg/opkg), Debian package (.deb), or RPM. The packages can then be upgraded using the package tools on the device, much like on a desktop distribution like Ubuntu or Fedora.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
|
Loading…
Reference in New Issue