public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] how to "git-bisect" in a portage-compatible way ?
Date: Wed, 10 Mar 2010 12:03:44 +0100	[thread overview]
Message-ID: <hn7uah$r3a$1@dough.gmane.org> (raw)

Hello,

Background info : I'm experiencing a bug and found out that the bug
doesn't appear with libdrm-2.4.11 (I kept an ebuild for this one in
/usr/local/portage/...), but it does occur with libdrm-2.4.13 (not sure
about the version numbers anymore, and I have yet to try 2.4.12, too,
but that's not the question)

So the general question is : if I want to use git-bisect (I have never
done that before, but today is a good time to try), I guess it means
I'll have to build libdrm outside portage : if so, once I'm finished
with hunting the bug, how to go back to the situation where portage does
everything for me ?

Some more precise questions :
- before I begin, should I first unmerge libdrm ?
- once I finished with bisecting, should I reemerge libdrm ? Will
portage overwrite files it may need to overwrite ? what about orphanned
files (if any) ?

I looked at the documentation list on gentoo.org, I did find a section
entitled "Non-portage maintained software", but this is not what I'm
looking for. Where else should I look at ?

thanks for your comments

Nicolas.




             reply	other threads:[~2010-03-10 11:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 11:03 Nicolas Richard [this message]
2010-03-10 16:08 ` [gentoo-user] Re: how to "git-bisect" in a portage-compatible way ? walt
2010-03-11 15:54   ` Nicolas Richard
2010-03-12  1:13     ` walt
2010-03-16  8:24       ` Nicolas Richard

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='hn7uah$r3a$1@dough.gmane.org' \
    --to=theonewiththeevillook@yahoo.fr \
    --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