All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Damien LEFEVRE" <lefevre.da@gmail.com>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] PREFERRED_VERSION
Date: Thu, 14 May 2020 11:43:43 +0300	[thread overview]
Message-ID: <CA+FhBv_i-EFUqsC8HQpfHJi2eBb4Qy9o1LG1bJpodHw1epOTqw@mail.gmail.com> (raw)
In-Reply-To: <20200514082033.5uukrrsvpp77upxv@qschulz>

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

OK thanks guys, that's what I though.

I did hack 1 since I could, but good to know the hack 2. in case this ever
happens for packages I'm not in control of.

Cheers,
-Damien

On Thu, May 14, 2020 at 11:20 AM Quentin Schulz <
quentin.schulz@streamunlimited.com> wrote:

> Hi Damienm
>
> On Thu, May 14, 2020 at 11:05:56AM +0300, Damien LEFEVRE wrote:
> > Hi,
> >
> > Should it be possible to set PREFERRED_VERSION in the image definition
> > files?
> >
>
> Conceptually, no. An image recipe is a recipe. Global data is global and
> local data is local. A recipe (image or package) set local data only.
>
> > I have 2 image files:
> > - image1.bb
> > - image2.bb : PREFERRED_VERSION_package_1.0.0
> >
> > I have a package with 2 versions:
> > - package_1.0.0.bb
> > - package_1.1.0.bb
> >
>
> Correct way is different distro or machine. Obviously the build impact
> is high for such as small difference in images.
>
> Two possible hacks to me:
> 1. package10_1.0.0.bb and package11_1.1.0.bb but then you need to manage
> the dependencies inside recipes (those (r)depending on package10 or
> package11). If it's a "final" package which isn't a dependency of
> anything else except the image, that's actually not too bad. Then in the
> image you add package10 or package11.
>
> 2. Have an intermediate recipe which RDEPENDS_${PN} += "package
> (=1.1.0)" and the other on "package (=1.0.0)" and install this
> intermediate recipe in the appropriate image.
>
> There are shortcomings in both hacks (otherwise they wouldn't be called
> that way :) ).
>
> Quentin
>

[-- Attachment #2: Type: text/html, Size: 2547 bytes --]

  reply	other threads:[~2020-05-14  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14  8:05 PREFERRED_VERSION Damien LEFEVRE
2020-05-14  8:12 ` [yocto] PREFERRED_VERSION Ross Burton
2020-05-14  8:20 ` Quentin Schulz
2020-05-14  8:43   ` Damien LEFEVRE [this message]
2020-05-14  8:32 ` ito

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=CA+FhBv_i-EFUqsC8HQpfHJi2eBb4Qy9o1LG1bJpodHw1epOTqw@mail.gmail.com \
    --to=lefevre.da@gmail.com \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=yocto@lists.yoctoproject.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 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.