All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Khem Raj <raj.khem@gmail.com>, bitflipper <forums@bitflipper.net>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: RE: [yocto] Bitbake + Patches
Date: Tue, 23 Aug 2022 11:41:32 +0000	[thread overview]
Message-ID: <fcfe7d1380ab4d2598cff5004028d419@axis.com> (raw)
In-Reply-To: <CAMKF1spvyQh1czn+HiKmppXBCO_tkor_3Ogfj6wguwA0x+tAyA@mail.gmail.com>

> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
> Behalf Of Khem Raj
> Sent: den 23 augusti 2022 00:29
> To: bitflipper <forums@bitflipper.net>
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Bitbake + Patches
> 
> On Mon, Aug 22, 2022 at 1:54 PM bitflipper <forums@bitflipper.net> wrote:
> >
> >
> >
> > I was told this was the right group to ask my question. If this is not
> right, please let me know.
> >
> > I am currently using  Zeus, and with Zeus, we get Apache v2.4.41. But I
> would like to get a later version of apache because there have been a few
> fixes related to cyber security. So I believe that, given we’re using
> Zeus, we can’t upgrade to the latest version of Apache given the current
> recipe that Zeus uses. Therefore I believe that the only way accomplish
> getting tho the latest version of apache with Zeus would to be ‘patch’
> the v2.4.41 version that comes with Zeus.
> >
> > Looking at the Bitbake manual, in section 4.1, it states the following:
> >
> > "BitBake takes several steps when fetching source code or files. The
> fetcher codebase deals with two distinct processes in order: obtaining the
> files from somewhere (cached or otherwise) and then unpacking those files
> into a specific location and perhaps in a specific way. Getting and
> unpacking the files is often optionally followed by patching. Patching,
> however, is not covered by this module."
> >
> >
> > The manual does not cover patching.
> >
> > Where can I get information on this process of patching something like
> apache or any other application that was add via IMAGE_INSTALL_append
> method.
> >
> > Any help pointing me to where this process might be documented is much
> appreciated.
> >
> 
> look into mega manual something like this would help
> https://docs.yoctoproject.org/dev-manual/common-tasks.html?highlight=writing+recipe#patching-code
> 
> > Thanks, Jim

You don't really need to go patching apache just to update it. What you 
need is to add a bbappend file in one of your own layers. Call it 
recipes-httpd/apache2/apache2_2.4.41.bbappend and make it contain:

FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"

LIC_FILES_CHKSUM = "file://LICENSE;md5=bddeddfac80b2c9a882241d008bb41c3"

PV = "2.4.54"

SRC_URI += "file://0008-Fix-perl-install-directory-to-usr-bin.patch \
            file://0009-support-apxs.in-force-destdir-to-be-empty-string.patch \
            file://0001-make_exports.awk-not-expose-the-path.patch"
SRC_URI_remove = "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"

You then also need to copy the three new patches and any other 
patches that differs between zeus and master and put them in your 
layer together with the bbappend file (in a subdirectory called 
"recipes-httpd/apache2/apache2").

The suggested contents of the bbappend above is based on the 
differences between the apache2 recipe in zeus and master.

//Peter


  reply	other threads:[~2022-08-23 11:41 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 [this message]
     [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

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=fcfe7d1380ab4d2598cff5004028d419@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=forums@bitflipper.net \
    --cc=raj.khem@gmail.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.