public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] scope of user patches via epatch
Date: Sat, 18 Nov 2017 13:19:17 -0600	[thread overview]
Message-ID: <be5209cb-cc61-b472-c147-955d84f7ce1c@gmail.com> (raw)
In-Reply-To: <20171118191035.2fxlx7uzftynbn26@matica.foolinux.mooo.com>

Ian Zimmerman wrote:
> Is there any way to make the patches under /etc/portage/patches
> applicable to more than a single exact version of each package?  Right
> now, every time I emerge -u I have to check if I have patches for a
> package on the updated list, and if so make a new subdirectory for the
> new version and copy or link the patches there [1].  This is a chore I
> could live without.  So my question is if there's any wildcard mechanism
> to match multiple versions.
>
> [1] Some fail to apply of course but that's ok, still less work to see
> which ones fail than to try checking separately each patch if it applies
> or not.
>

Unless I want it to apply only to a specific version, I don't use
versions.  This is a example of how the directory/files are for a patch
that allows kwrite to run as root. 

/etc/portage/patches/kde-apps/kwrite/allow-root.patch 

If I wanted it to apply to only one version, I could add that like you
do on yours.  Since you want yours to apply to all version like mine,
make yours look sort of like mine.  It works here so it should work for
you as well, if the patch works of course.  ;-)

Dale

:-)  :-) 


      reply	other threads:[~2017-11-18 19:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18 19:10 [gentoo-user] scope of user patches via epatch Ian Zimmerman
2017-11-18 19:19 ` Dale [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=be5209cb-cc61-b472-c147-955d84f7ce1c@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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