[Question] "global" package list used to bump up customer packages

[Question] "global" package list used to bump up customer packages

[Mans Zigher]

Hi,

I have a problem getting my customer to understand how to work with
OE. They have a set of private packages that they continuously need to
bump up to use the latest version. The packages are stored up in an
artifactory server. I have an idea of maybe helping them out by adding
a manifest file containing a couple of entries for each package

VERSION = "0.25.6"
SRC_URI[md5sum] = "0d6bc46bb69b2a0dce0c042d27b4f25c"
SRC_URI[sha256sum] =
"c20ea63a5e2f24e25d91e5cdfaa6b4b3735739d6170bea7b2b7d429fc397b718"

This manifest should then be pulled into the bitbake environment so
that the packages can read these entries and download what is needed.
Any comments regarding this potential solution would be greatly
appreciated.

Also I have a faint memory of seeing something similar solution so if
you know if something already exists then I would appreciate if you
could let me know.

BR

Re: [OE-core] [Question] "global" package list used to bump up customer packages

[Richard Purdie]

On Fri, 2021-02-19 at 09:53 +0100, Mans Zigher wrote:
> Hi,
> 
> I have a problem getting my customer to understand how to work with
> OE. They have a set of private packages that they continuously need to
> bump up to use the latest version. The packages are stored up in an
> artifactory server. I have an idea of maybe helping them out by adding
> a manifest file containing a couple of entries for each package
> 
> VERSION = "0.25.6"
> SRC_URI[md5sum] = "0d6bc46bb69b2a0dce0c042d27b4f25c"
> SRC_URI[sha256sum] =
> "c20ea63a5e2f24e25d91e5cdfaa6b4b3735739d6170bea7b2b7d429fc397b718"
> 
> This manifest should then be pulled into the bitbake environment so
> that the packages can read these entries and download what is needed.
> Any comments regarding this potential solution would be greatly
> appreciated.
> 
> Also I have a faint memory of seeing something similar solution so if
> you know if something already exists then I would appreciate if you
> could let me know.

Are you thinking of AUTOREV? That works if the fetcher has support
for the source control system being used, e.g. git or subversion but
I'm not sure it would work for artifactory without a dedicated fetcher
module.

Certainly generating an include file like this is one way to handle
this. You can use package-name overrides, e.g.:

VERSION_pn-somepackagename = "0.1.2"

although its harder to do with flags, you might have to put those via
an intermediate variable:

SRCURISHA256_pn-somepackagename = "XXX"

then in the recipe:

SRC_URI[sha256sum] = "${SRCURISHA256}"

Cheers,

Richard

Re: [OE-core] [Question] "global" package list used to bump up customer packages

[Mans Zigher]

Hi,

Thanks for the reply. My customer are not really interested in going
into multiple recipes so that is why I am thinking of having a
manifest file for them to update packages in one location. I still
want to have some kind of step where someone approves the "pumping" so
even if AUTOREV could be an alternative I am not sure that is the
solution but I will investigate that. The pn-somepackage variable is
likely part of the solution.

BR

Den fre 19 feb. 2021 kl 18:38 skrev Richard Purdie
<richard.purdie@linuxfoundation.org>:
>
> On Fri, 2021-02-19 at 09:53 +0100, Mans Zigher wrote:
> > Hi,
> >
> > I have a problem getting my customer to understand how to work with
> > OE. They have a set of private packages that they continuously need to
> > bump up to use the latest version. The packages are stored up in an
> > artifactory server. I have an idea of maybe helping them out by adding
> > a manifest file containing a couple of entries for each package
> >
> > VERSION = "0.25.6"
> > SRC_URI[md5sum] = "0d6bc46bb69b2a0dce0c042d27b4f25c"
> > SRC_URI[sha256sum] =
> > "c20ea63a5e2f24e25d91e5cdfaa6b4b3735739d6170bea7b2b7d429fc397b718"
> >
> > This manifest should then be pulled into the bitbake environment so
> > that the packages can read these entries and download what is needed.
> > Any comments regarding this potential solution would be greatly
> > appreciated.
> >
> > Also I have a faint memory of seeing something similar solution so if
> > you know if something already exists then I would appreciate if you
> > could let me know.
>
> Are you thinking of AUTOREV? That works if the fetcher has support
> for the source control system being used, e.g. git or subversion but
> I'm not sure it would work for artifactory without a dedicated fetcher
> module.
>
> Certainly generating an include file like this is one way to handle
> this. You can use package-name overrides, e.g.:
>
> VERSION_pn-somepackagename = "0.1.2"
>
> although its harder to do with flags, you might have to put those via
> an intermediate variable:
>
> SRCURISHA256_pn-somepackagename = "XXX"
>
> then in the recipe:
>
> SRC_URI[sha256sum] = "${SRCURISHA256}"
>
> Cheers,
>
> Richard
>
>
>