linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: howarth@bromo.med.uc.edu (Jack Howarth)
To: linuxppc-dev@lists.linuxppc.org
Subject: new XFree86 4.0 test rpms
Date: Sun, 19 Mar 2000 14:44:05 -0800 (PST)	[thread overview]
Message-ID: <200003192244.OAA22419@bromo.med.uc.edu> (raw)


    I have built new -0.2d XFree86 v4.0 test rpms and placed them
in my public_html on entropy.crashing.org. These can be accessed
from http://entropy.crashing.org/~howarth/. The new rpms correct
a flaw in redhat's -0.2 spec which misplaced support files. The
new rpms also eliminate the driver packages that currently don't
work properly. A new XF86Config is in the top level directory
which was generated from XFree86 -configure and is more correct
than the previous one. Xkb is still disabled as there is an unresolved
problem on usb keyboards.
                          Jack Howarth

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-03-19 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-19 22:44 Jack Howarth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-20 10:00 new XFree86 4.0 test rpms Michel D?nzer

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=200003192244.OAA22419@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).