Closed GoogleCodeExporter closed 9 years ago
in steps 4 means opkg_upgrade_package not opkg_install_package
Original comment by alex569....@gmail.com
on 5 Nov 2014 at 9:18
What arguments are you passing to opkg_install_package? Are you passing the
path to the package file or just the package name (which would be
"bison-locale-da" in this case)?
Original comment by paul.betafive
on 5 Nov 2014 at 10:30
I pass full path as following
/media/disk/bison-locale-da_3.3-r1_cortexa9-vfp-neon.ipk
Original comment by alex569....@gmail.com
on 5 Nov 2014 at 11:05
opkg_install_package() only supports the use of package names not full paths to
package files. The current libopkg API is deprecated so I'm not planning to add
this support.
You should however be able to call opkg_prepare_url_for_install to load the
package file and get the package name. For example, this might work:
char *pkg_name;
opkg_prepare_url_for_install(pkg_path, &pkg_name);
opkg_install_pkg(pkg_name);
free(pkg_name);
The old API has a lot of problems like this which is why it is deprecated. I'd
recommend you interact with opkg via the command line interface until a new
libopkg API arrives in opkg v0.4.0 or later.
Original comment by paul.betafive
on 9 Nov 2014 at 5:23
Sorry, that should be opkg_install_package(pkg_name, ...) not opkg_install_pkg.
The API even confuses me!
Original comment by paul.betafive
on 9 Nov 2014 at 5:24
Original issue reported on code.google.com by
alex569....@gmail.com
on 5 Nov 2014 at 9:15Attachments: