public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Djamil ESSAISSI <djamil@francexpress.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Portage question
Date: Mon Aug 27 08:48:01 2001	[thread overview]
Message-ID: <20010827165311.0981f20b.djamil@francexpress.com> (raw)
In-Reply-To: <000b01c12da8$33f78660$0100a8c0@chrislaptop>

well well well , tell me , have you ever screwed around with a voodoo3 lately ? i'm having a hard time getting some descent framerate out of it ...at 4.1.0 

On Sat, 25 Aug 2001 21:54:57 +0100
"Christopher Burgess" <chris@uknet.demon.co.uk> wrote:

:-)How do I emerge a package, but before it's built apply my own patches
:-)to the
:-)source?
:-)e.g. use emerge to download the source, unpack it etc - stop it here,
:-)do my
:-)own mods to the source - then let emerge build and install it.
:-)
:-)The main reason is that I am having some problems with xfree4.1.0
:-)locking up
:-)on with my radeon card (on startx it just locks up and sends the
:-)monitor
:-)into power save mode) unless I use the "noaccel" option which is
:-)horribly
:-)slow and I don't get DRI with that. I have searched the xfree mailing
:-)lists
:-)and found a small hand patch which might fix it, but rather than
:-)downloading
:-)it manually (the xfree source) I'd rather use emerge. However to be
:-)able to
:-)do this on other packages (modifying the source before emerge builds)
:-)would
:-)be useful.
:-)Also is there anyone else having a Radeon problem with xfree?
:-)
:-)Thanks
:-)
:-)Chris
:-)
:-)
:-)_______________________________________________
:-)gentoo-dev mailing list
:-)gentoo-dev@cvs.gentoo.org
:-)http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
:-)


-- 
================================================
System Administrateur / Support Technique
Tel:01.58.64.22.44 - Fax:01.58.64.26.81

Djamil ESSAISSI
============================================================
www.francexpress.com - www.serveur-express.com
Hébergement professionnel & Location de serveurs dédiés
Tel:01.58.64.26.44 Fax:01.58.64.26.81 djamil@francexpress.com



  parent reply	other threads:[~2001-08-27 14:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-25 14:57 [gentoo-dev] Portage question Christopher Burgess
2001-08-25 15:06 ` Mikael Hallendal
2001-08-25 15:20   ` Daniel Robbins
2001-08-25 15:32     ` Mikael Hallendal
2001-08-27  8:48 ` Djamil ESSAISSI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-01 23:09 [gentoo-dev] portage question Leon Chiver
2002-10-02  7:22 ` Henti Smith
2002-10-02  7:39   ` Evan Read
2002-10-02  9:02     ` Alexander Gretencord
2002-10-02  9:12       ` Paul de Vrieze
2002-10-02 12:28         ` Toby Dickenson
2002-10-02 12:34         ` Toby Dickenson
2002-10-02 10:06       ` Henti Smith
2002-10-02 11:53         ` Christian Skarby
2002-10-02 11:54           ` Henti Smith
2002-10-02 12:23             ` Christian Skarby
2002-10-02 12:26               ` Henti Smith
2002-10-02 14:12               ` Alexander Gretencord
2001-08-25 15:26 [gentoo-dev] Portage question Christopher Burgess
2001-08-25 15:36 ` Mikael Hallendal
2001-01-30 21:23 [gentoo-dev] useradd q Dave Bresson
2001-01-30 21:57 ` Achim Gottinger
2001-01-30 23:14   ` [gentoo-dev] portage question John McCaskey

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=20010827165311.0981f20b.djamil@francexpress.com \
    --to=djamil@francexpress.com \
    --cc=gentoo-dev@cvs.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