From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.com
Subject: Re: [ptxdist] local rule makefile include $(PTXDIST_TOPDIR)/rules/...
Date: Fri, 3 Aug 2018 12:52:49 -0400 [thread overview]
Message-ID: <CAMwGMjwzFwrcwFN29WXy_Ur3OBnRNfo-9E2iWM1gy5hYtotQNg@mail.gmail.com> (raw)
In-Reply-To: <CAMwGMjz2vzMa=0a2Hdq3vZcEm70j_vj_-yJuC9FGC2Ku6pMfPQ@mail.gmail.com>
Hi,
I was able to solve my problem below :)
I defined my local rules file as follows in order to "fool" the
ptxd_is_pkg_makefile() function in
scrips/lib/ptxd_make_world_check_src.sh:
~/git/rootfs$ cat rules/systemd.make
#
# We provide this package
#
OVERLAY_PACKAGES-$(PTXCONF_SYSTEMD) += systemd
SYSTEMD_SERIES_SHA256 :=
0560688f87a3232377c24263245e401629da11de366e52e40275e142a5024268
include $(PTXDIST_TOPDIR)/rules/systemd.make
The choice of "OVERLAY_" prefix was arbitrary. It doesn't matter what
the prefix is before the *PACKAGES- line is as long as it is
"^[A-Z_]*" and not the same as the one found in
$(PTXDIST_TOPDIR)/rules/*.make file
-Jon
On Fri, Aug 3, 2018 at 4:25 AM Jon Ringle <jon@ringle.org> wrote:
>
> Hi,
>
> As a follow up to my patch "Detect changes in package patch series",
> I'd like to be able to further this by having the ability to maintain
> my own patch series for a package without having to be forced to also
> maintain the package's rules makefile as well. To try to achieve this
> I tried having the following content in my local rule makefile:
>
> ~/git/rootfs$ cat rules/systemd.make
> SYSTEMD_SERIES_SHA256 := # I want to maintain only my patch series locally...
> include $(PTXDIST_TOPDIR)/rules/systemd.make
>
> Unfortunately, this does not work as desired:
> ~/git/rootfs$ ~/git/ptxdist/bin/ptxdist --force extract systemd
>
> -----------------------
> target: systemd.extract
> -----------------------
>
> patchin: no patches found
> finished target systemd.extract
>
> In fact, all targets given to this package don't behave:
> ~/git/rootfs$ ~/git/ptxdist/bin/ptxdist --force targetinstall systemd
>
> ----------------------------------
> target: systemd.targetinstall.post
> ----------------------------------
>
> finished target systemd.targetinstall.post
>
> Any ideas on either other approaches to tackle this problem or
> direction on where to start hacking at the ptxdist code to make my
> approach workable?
>
> Regards,
> -Jon
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-08-03 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 8:25 Jon Ringle
2018-08-03 16:52 ` Jon Ringle [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=CAMwGMjwzFwrcwFN29WXy_Ur3OBnRNfo-9E2iWM1gy5hYtotQNg@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.com \
--cc=ptxdist@pengutronix.de \
/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