mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.com
Subject: [ptxdist] local rule makefile include $(PTXDIST_TOPDIR)/rules/...
Date: Fri, 3 Aug 2018 04:25:15 -0400	[thread overview]
Message-ID: <CAMwGMjz2vzMa=0a2Hdq3vZcEm70j_vj_-yJuC9FGC2Ku6pMfPQ@mail.gmail.com> (raw)

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

             reply	other threads:[~2018-08-03  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03  8:25 Jon Ringle [this message]
2018-08-03 16:52 ` Jon Ringle

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='CAMwGMjz2vzMa=0a2Hdq3vZcEm70j_vj_-yJuC9FGC2Ku6pMfPQ@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