From: Paul Barker <paul@paulbarker.me.uk>
To: Marco <koansoftware@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Upgrade to a package with all its dependency without network
Date: Mon, 5 May 2014 15:29:33 +0000 [thread overview]
Message-ID: <20140505152931.GA26865@gmail.com> (raw)
In-Reply-To: <53679D4E.6060202@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2425 bytes --]
On Mon, May 05, 2014 at 04:16:46PM +0200, Marco wrote:
> Hello,
> I need to be able to upgrade to a package with all its dependency chain on a
> target system that does not have access to the network.
>
> I'm trying to understand what may be the best and also the simplest
> solution.
> Perhaps there is already this functionality in OE/Yocto?
>
> I thought to implement a new opkg feture so that I can to generate the list
> of dependencies of a package and then extract the packages from OE/Yocto
> using a script or an application.
opkg v0.2.x (the latest release series) doesn't really support this behaviour
very well. The caching logic just doesn't work. For example, I have a board
connected at the minute with a feed configured so I tried this:
opkg install --download-only ncurses-terminfo
ifdown eth0
opkg install ncurses-terminfo
You'd hope that would pick up the package files from the cache but it doesn't.
So even if you put the files there yourself, you may no have a simple way to
install them.
An interim solution I can see is to put all the packages you want in one
directory then run 'opkg-make-index' from opkg-utils on that directory so that
it is a complete package feed. Then add that as a source in
/etc/opkg/base-feeds.conf.
The development branch of opkg which will become v0.3.x has much better cache
logic, it just needs finishing off and tidying up. I'm very busy at the minute
but it's getting there. Any help to close the remaining issues so it can be
released would be appreciated!
>
> Another possibility would be to extend the operation of bitbake so I pull
> out the package and dependencies putting them in a dedicated directory to be
> moved on the target for the update.
>
> For now I'm just analyzing what may be the possibilities and I'd love to
> have any comments or advice from someone more experienced than me on this
> topic.
>
> Thanks
> --
> Marco Cavallini | KOAN sas | Bergamo - Italia
> embedded and real-time software engineering
> Phone:+39-035-255.235 - Fax:+39-178-22.39.748
> http://www.KoanSoftware.com
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Paul Barker
Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk
[-- Attachment #2: Type: application/pgp-signature, Size: 501 bytes --]
next prev parent reply other threads:[~2014-05-05 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 14:16 Upgrade to a package with all its dependency without network Marco
2014-05-05 15:29 ` Paul Barker [this message]
2014-05-07 7:54 ` Marco
2014-05-07 11:31 ` Paul Barker
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=20140505152931.GA26865@gmail.com \
--to=paul@paulbarker.me.uk \
--cc=koansoftware@gmail.com \
--cc=openembedded-core@lists.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