public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Zaman <perfinion@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: cor@cor.za.net
Subject: Re: [gentoo-dev] xf86-input-evdev patch problem
Date: Mon, 12 Oct 2015 15:03:22 +0800	[thread overview]
Message-ID: <20151012070322.GA4274@meriadoc> (raw)
In-Reply-To: <1444625787.4478.24.camel@cor.za.net>

On Mon, Oct 12, 2015 at 06:56:27AM +0200, Cor Legemaat wrote:
> Hi:
>  
> I created a ebuild with a patch for xf86-input-evdev to try and 
> debounce my mouse button. The ebuild is at 
> https://github.com/cor-mt/portage-overlay/blob/master/x11-drivers/xf86-input-evdev/xf86-input-evdev-2.9.2-r1.ebuild
>  it compile and install fine but with it installed neither the 
> keyboard nor mouse is working. If I am correct it should install 100% 
> the same as from gentoo without the "debounce" use flag but it gives 
> the same symptoms.
>  
> What am I doing wrong?

So the problem here is the "inherit linux-info xorg-2" line.
The xorg-2 eclass defines few default phase functions which you have
overridden.

If you want to patch the source you should be doing something like this:
src_prepare() {
	use debounce && epatch ${FILESDIR}/your-patch

	xorg-2_src_prepare # this will call the xorg-2 eclass
	#defined phase function to do the rest of the work
}

Alternatively, if you just want to apply that patch, you are probably
better off using epatch_user.
Drop your patch in
/etc/portage/patches/x11-drivers/xf86-input-evdev/your-name.patch
and the eclasses will automatically apply the patch. you do not have to
make your own ebuild just to apply the patch.

This has more info: https://wiki.gentoo.org/wiki//etc/portage/patches

-- Jason



  reply	other threads:[~2015-10-12  7:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  4:56 [gentoo-dev] xf86-input-evdev patch problem Cor Legemaat
2015-10-12  7:03 ` Jason Zaman [this message]
2015-10-19  3:50   ` Cor Legemaat

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=20151012070322.GA4274@meriadoc \
    --to=perfinion@gentoo.org \
    --cc=cor@cor.za.net \
    --cc=gentoo-dev@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