* [RFC] Upgrade to a package with all its dependency without network
@ 2014-05-06 7:41 Marco
2014-05-06 17:03 ` Khem Raj
2014-05-15 12:47 ` Bryan Evenson
0 siblings, 2 replies; 3+ messages in thread
From: Marco @ 2014-05-06 7:41 UTC (permalink / raw)
To: yocto@yoctoproject.org
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.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC] Upgrade to a package with all its dependency without network
2014-05-06 7:41 [RFC] Upgrade to a package with all its dependency without network Marco
@ 2014-05-06 17:03 ` Khem Raj
2014-05-15 12:47 ` Bryan Evenson
1 sibling, 0 replies; 3+ messages in thread
From: Khem Raj @ 2014-05-06 17:03 UTC (permalink / raw)
To: koansoftware; +Cc: yocto@yoctoproject.org
Marco
On Tue, May 6, 2014 at 12:41 AM, Marco <koansoftware@gmail.com> 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.
>
> 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.
>
I would say file a feature/enhancement request in Yocto bugzilla so it
does not get lost.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC] Upgrade to a package with all its dependency without network
2014-05-06 7:41 [RFC] Upgrade to a package with all its dependency without network Marco
2014-05-06 17:03 ` Khem Raj
@ 2014-05-15 12:47 ` Bryan Evenson
1 sibling, 0 replies; 3+ messages in thread
From: Bryan Evenson @ 2014-05-15 12:47 UTC (permalink / raw)
To: koansoftware@gmail.com, yocto@yoctoproject.org
Marco,
> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Marco
> Sent: Tuesday, May 06, 2014 3:42 AM
> To: yocto@yoctoproject.org
> Subject: [yocto] [RFC] Upgrade to a package with all its dependency without
> network
>
> 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.
>
> 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.
Go to your local.conf and add the following:
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
This will generate build history information for each image you build. Included in that build history is the list of packages installed in the image. So if you are building core-image-minimal, there will be a file called "tmp/buildhistory/images/{arch}/eglibc/core-image-minimal/installed-packages.txt" under your Yocto temp directory that lists all the packages installed on that image. I have a script that I am using to build a package feed folder that only contains the packages I have installed on that image. The script is highly customized for my use (almost everything is hardcoded) but I'd be willing to work with someone to make it useful for more people if someone thinks it would be useful.
Regards,
Bryan
>
> 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
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-15 12:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-06 7:41 [RFC] Upgrade to a package with all its dependency without network Marco
2014-05-06 17:03 ` Khem Raj
2014-05-15 12:47 ` Bryan Evenson
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.