Yocto Project Discussions
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: forums <forums@bitflipper.net>
Cc: "Yocto (yocto@lists.yoctoproject.org)"
	<yocto@lists.yoctoproject.org>,
	Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Subject: Re: [yocto] Bitbake + Patches
Date: Tue, 30 Aug 2022 16:22:57 -0400	[thread overview]
Message-ID: <101418e6-b123-991a-7192-0e4cb13fe4bb@windriver.com> (raw)
In-Reply-To: <9222c257155a4d5aa93db2f0f9d1047b@axis.com>

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

On 2022-08-26 10:03, Peter Kjellerstedt wrote:
>
> [ In the future, please make sure to reply to list and not just to me. ]
>
> [ Top posting since Outlook doesn’t support inline responses to HTML 
> mails. ]
>
> No, you are supposed to copy the suggest text for the bbappend 
> verbatim, with the exception of theSRC_URI[md5sum]which need to be 
> corrected to match the actual MD5 sum (which bitbake will tell you 
> when you try to build). The suggested additions/deletions for 
> SRC_URIin the bbappend I suggested should be correct as specified, 
> based on the differences between the apache2 recipe in Zeus and 
> master. You will also need to copy the three new patch files from 
> master of meta-webserver, and any of the other patches that have been 
> updated between Zeus and master. Changing PVtakes care of the actual 
> update of the code to the new version (since it determines which tar 
> ball is fetched from upstream).
>
> //Peter
>
Jim,

In addition to all of this, note that the 'zeus' branch was only 
supported until
August 2020:

https://wiki.yoctoproject.org/wiki/Releases


If you want longer term support to be able to use a well maintained
release of Yocto for 5, 10 or 15 years, there are vendors, including
Wind River, that supply those services. See:
https://www.yoctoproject.org/ecosystem/members/

Good luck,

../Randy


> *From:*forums <forums@bitflipper.net>
> *Sent:* den 26 augusti 2022 14:21
> *To:* Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> *Subject:* Re: [yocto] Bitbake + Patches
>
>         FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"
>
>         LIC_FILES_CHKSUM =
>         "file://LICENSE;md5=bddeddfac80b2c9a882241d008bb41c3
>         <file://LICENSE;md5=bddeddfac80b2c9a882241d008bb41c3>"
>
>         PV = "2.4.54"
>
>         SRC_URI +=
>         "file://0008-Fix-perl-install-directory-to-usr-bin.patch
>         <file://0008-Fix-perl-install-directory-to-usr-bin.patch> \
>         file://0009-support-apxs.in-force-destdir-to-be-empty-string.patch
>         <file:///0009-support-apxs.in-force-destdir-to-be-empty-string.patch> \
>         file://0001-make_exports.awk-not-expose-the-path.patch
>         <file:///0001-make_exports.awk-not-expose-the-path.patch>"
>         SRC_URI_remove = "file://apache-configure_perlbin.patch
>         <file://apache-configure_perlbin.patch>"
>
>         SRC_URI[md5sum] = "<I don't have this at hand, but bitbake
>         will tell you what it should be>"
>         SRC_URI[sha256sum] =
>         "eb397feeefccaf254f8d45de3768d9d68e8e73851c49afd5b7176d1ecf80c340"
>
> H Peter. I have t admin, looking at the above bbappend, its really 
> confusing to me. I’ve looked at some of the documents on bitbake and I 
> just can’t find anything to teach me how to put a bbappend together to 
> accomplish upgrading an application.
>
> Like for example:
>
>         SRC_URI +=
>         "file://0008-Fix-perl-install-directory-to-usr-bin.patch
>         <file://0008-Fix-perl-install-directory-to-usr-bin.patch>
>
> I believe this one should be:
>
> SRC_URI += file:/usr/bin/patch
>
> The next one:
>
>         file://0009-support-apxs.in-force-destdir-to-be-empty-string.patch
>         <file:///0009-support-apxs.in-force-destdir-to-be-empty-string.patch>
>
> I’ve no idea what this one will nee to be.
>
> And this one:
>
>         file://0001-make_exports.awk-not-expose-the-path.patch
>         <file:///0001-make_exports.awk-not-expose-the-path.patch>
>
> I don’t know what is supposed to go here either.
>
> Then the SRC_URI_remove will be a pointer to the file containing the 
> patches containing the diff’e between apache 12.4.1 and apache 2.4.54 
> ? I don’t think you can create a single patch file containing diff’s 
> between multiple versions can you? I think it would have to be diff’s 
> between apache 2.4.41 and 2.4.42. Right. Totally confused as to what 
> to do here.
>
> Any further help appreciated.
>
> If you know of a resource for me to reference please pass it on. I 
> just don’t see any clear documentation that explains how to construct 
> a bbappend file.
>
> Thanks, Jim
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#57911):https://lists.yoctoproject.org/g/yocto/message/57911
> Mute This Topic:https://lists.yoctoproject.org/mt/93191096/3616765
> Group Owner:yocto+owner@lists.yoctoproject.org
> Unsubscribe:https://lists.yoctoproject.org/g/yocto/unsub  [randy.macleod@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

-- 
# Randy MacLeod
# Wind River Linux

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

      parent reply	other threads:[~2022-08-30 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 20:54 Bitbake + Patches forums
2022-08-22 22:29 ` [yocto] " Khem Raj
2022-08-23 11:41   ` Peter Kjellerstedt
     [not found]     ` <B58205E1-72E9-41F6-9A52-A440A62C3C6B@bitflipper.net>
2022-08-24 14:13       ` Peter Kjellerstedt
     [not found]         ` <0C54FD2B-AEAB-4425-9CEB-FFCA85458A16@bitflipper.net>
2022-08-26 14:03           ` Peter Kjellerstedt
2022-08-29  2:49             ` forums
     [not found]             ` <170FB0FB9A5D94E8.11791@lists.yoctoproject.org>
2022-08-29 19:34               ` forums
     [not found]               ` <170FE7D455D5B425.21714@lists.yoctoproject.org>
2022-08-29 20:06                 ` forums
2022-08-29 22:06                   ` forums
2022-09-06 18:01                     ` Peter Kjellerstedt
2022-08-30 20:22             ` Randy MacLeod [this message]

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=101418e6-b123-991a-7192-0e4cb13fe4bb@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=forums@bitflipper.net \
    --cc=peter.kjellerstedt@axis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox