Package manager for GDP: smart?
jeremiah.foster at pelagicore.com
Thu Jun 2 13:03:25 EDT 2016
On Thu, Jun 2, 2016 at 4:33 PM, Streif, Rudolf <rstreif at jaguarlandrover.com>
> Hi Changhyeok,
>> In the future, we need to separate release and dev image.
>> That is probably mostly a function of resources for maintenance and
> testing. However, one model could be that we only test the release image to
> the full depth as you propose to only add packages to the dev image.
What do we mean when we say "release" image. Is this the image that is
meant to be run on the target? Shouldn't we include the term "target"
>> release image has only fota client.
>> Dev has fota client, package manager (ex, rpm), and dev tools.
>> The release image will still require the package manager (rpm) even with
> the SOTA client as the latter defers to the platform package manager to
> install, remove, update packages and maintain the package database.
> My question is, if you are also suggesting to add SmartPM to the dev
> image. If so, then we would also need to set up the server-side
> infrastructure for that (probably a HTTP server) in addition to the SOTA
> My rationale for pushing SOTA is to vet the technology through testing
> with an end-to-end setup.
>> So IMO currently it's good to maintain both of them in GDP.
>> In my understanding, sota server is also fully opensource right?
>> Yes, it is an open source GENIVI project. You can find the source on
> GitHub at https://github.com/GENIVI/rvi_sota_server.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the genivi-projects