Always patch latest upstream package

Always patch latest upstream package

[jlac]

[-- Attachment #1.1: Type: text/plain, Size: 179 bytes --]

Hi,

I would like apply patch on an upstream package but without specify 
version, like <recipe>_%.bbappend in yocto project. 
How recipe must be name ? or How proceed?

Regards,

[-- Attachment #1.2: Type: text/html, Size: 251 bytes --]

Re: Always patch latest upstream package

[Jan Kiszka]

On 24.09.20 21:31, jlac wrote:
> Hi,
> 
> I would like apply patch on an upstream package but without specify 
> version, like <recipe>_%.bbappend in yocto project.
> How recipe must be name ? or How proceed?

Do you mean patching an original (or third-party) Debian package? Then 
have a look at [1]. A "real-word" case is [2].

Note, though, that you can track debian stable updates this way but not 
major package version update. That's due to the original package, when 
pulled via SRC_URI = "apt://${PN}", is unpacked to a path containing the 
major version. And that path has to be known in order to set ${S}. There 
was a lengthy discussion about that issue in [3], but we found not 
better solution.

Jan

[1] https://github.com/ilbers/isar/tree/master/meta-isar/recipes-app/hello
[2] 
https://github.com/siemens/meta-iot2050/tree/master/recipes-security/openssl
[3] 
https://groups.google.com/d/msgid/isar-users/da04421b-fb4b-f5c1-539e-6053ffc412d0%40siemens.com

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Re: Always patch latest upstream package

[jlacvdr]

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

my question concern original package, like openssl in your example
too bad doesn't solution exist, even a trick with <orig version>

Thanks for info & links

Le ven. 25 sept. 2020 à 08:16, Jan Kiszka <jan.kiszka@siemens.com> a écrit :

> On 24.09.20 21:31, jlac wrote:
> > Hi,
> >
> > I would like apply patch on an upstream package but without specify
> > version, like <recipe>_%.bbappend in yocto project.
> > How recipe must be name ? or How proceed?
>
> Do you mean patching an original (or third-party) Debian package? Then
> have a look at [1]. A "real-word" case is [2].
>
> Note, though, that you can track debian stable updates this way but not
> major package version update. That's due to the original package, when
> pulled via SRC_URI = "apt://${PN}", is unpacked to a path containing the
> major version. And that path has to be known in order to set ${S}. There
> was a lengthy discussion about that issue in [3], but we found not
> better solution.
>
> Jan
>
> [1] https://github.com/ilbers/isar/tree/master/meta-isar/recipes-app/hello
> [2]
>
> https://github.com/siemens/meta-iot2050/tree/master/recipes-security/openssl
> [3]
>
> https://groups.google.com/d/msgid/isar-users/da04421b-fb4b-f5c1-539e-6053ffc412d0%40siemens.com
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>

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