diff options
authorquinn <quinn@d7aaf104-2d23-0410-ae22-9d23157bf5a3>2006-10-20 19:16:49 +0000
committerquinn <quinn@d7aaf104-2d23-0410-ae22-9d23157bf5a3>2006-10-20 19:16:49 +0000
commit202188c381fe8a53e262d414835cfe9caef07681 (patch)
parent5d07289b5b678c212eeed409bd846db1caec508e (diff)
not ever really needed...
git-svn-id: file:///beryl/trunk@715 d7aaf104-2d23-0410-ae22-9d23157bf5a3
25 files changed, 0 insertions, 826 deletions
diff --git a/xorg-sched-yield-hack/AUTHORS b/xorg-sched-yield-hack/AUTHORS
deleted file mode 100644
index 4bc2927..0000000
--- a/xorg-sched-yield-hack/AUTHORS
+++ /dev/null
@@ -1 +0,0 @@
diff --git a/xorg-sched-yield-hack/COPYING b/xorg-sched-yield-hack/COPYING
deleted file mode 100644
index 623b625..0000000
--- a/xorg-sched-yield-hack/COPYING
+++ /dev/null
@@ -1,340 +0,0 @@
- Version 2, June 1991
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
- Preamble
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
- The precise terms and conditions for copying, distribution and
-modification follow.
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
- How to Apply These Terms to Your New Programs
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- GNU General Public License for more details.
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-Also add information on how to contact you by electronic and paper mail.
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
- Gnomovision version 69, Copyright (C) year name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
diff --git a/xorg-sched-yield-hack/ChangeLog b/xorg-sched-yield-hack/ChangeLog
deleted file mode 100644
index e69de29..0000000
--- a/xorg-sched-yield-hack/ChangeLog
+++ /dev/null
diff --git a/xorg-sched-yield-hack/INSTALL b/xorg-sched-yield-hack/INSTALL
deleted file mode 100644
index 23e5f25..0000000
--- a/xorg-sched-yield-hack/INSTALL
+++ /dev/null
@@ -1,236 +0,0 @@
-Installation Instructions
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
-Software Foundation, Inc.
-This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
-Basic Installation
-These are generic installation instructions.
- The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation. It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions. Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
- It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring. (Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.)
- If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release. If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
- The file `' (or `') is used to create
-`configure' by a program called `autoconf'. You only need
-`' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
-The simplest way to compile this package is:
- 1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
- Running `configure' takes awhile. While running, it prints some
- messages telling which features it is checking for.
- 2. Type `make' to compile the package.
- 3. Optionally, type `make check' to run any self-tests that come with
- the package.
- 4. Type `make install' to install the programs and any data files and
- documentation.
- 5. You can remove the program binaries and object files from the
- source code directory by typing `make clean'. To also remove the
- files that `configure' created (so you can compile the package for
- a different kind of computer), type `make distclean'. There is
- also a `make maintainer-clean' target, but that is intended mainly
- for the package's developers. If you use it, you may have to get
- all sorts of other programs in order to regenerate files that came
- with the distribution.
-Compilers and Options
-Some systems require unusual options for compilation or linking that the
-`configure' script does not know about. Run `./configure --help' for
-details on some of the pertinent environment variables.
- You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment. Here
-is an example:
- ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
- *Note Defining Variables::, for more details.
-Compiling For Multiple Architectures
-You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
- If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory. After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
-Installation Names
-By default, `make install' installs the package's commands under
-`/usr/local/bin', include files under `/usr/local/include', etc. You
-can specify an installation prefix other than `/usr/local' by giving
-`configure' the option `--prefix=PREFIX'.
- You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files. If you
-pass the option `--exec-prefix=PREFIX' to `configure', the package uses
-PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files still use the regular prefix.
- In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files. Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
- If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-Optional Features
-Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System). The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
- For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-Specifying the System Type
-There may be some features `configure' cannot figure out automatically,
-but needs to determine by the type of machine the package will run on.
-Usually, assuming the package is built to be run on the _same_
-architectures, `configure' can figure that out, but if it prints a
-message saying it cannot guess the machine type, give it the
-`--build=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-where SYSTEM can have one of these forms:
- See the file `config.sub' for the possible values of each field. If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
- If you are _building_ compiler tools for cross-compiling, you should
-use the option `--target=TYPE' to select the type of system they will
-produce code for.
- If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-Sharing Defaults
-If you want to set default values for `configure' scripts to share, you
-can create a site shell script called `' that gives default
-values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/' if it exists, then
-`PREFIX/etc/' if it exists. Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-Defining Variables
-Variables not defined in a site shell script can be set in the
-environment passed to `configure'. However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost. In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'. For example:
- ./configure CC=/usr/local2/bin/gcc
-causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script). Here is a another example:
- /bin/bash ./configure CONFIG_SHELL=/bin/bash
-Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
-configuration-related scripts to be executed by `/bin/bash'.
-`configure' Invocation
-`configure' recognizes the following options to control how it operates.
- Print a summary of the options to `configure', and exit.
- Print the version of Autoconf used to generate the `configure'
- script, and exit.
- Enable the cache: use and save the results of the tests in FILE,
- traditionally `config.cache'. FILE defaults to `/dev/null' to
- disable caching.
- Alias for `--cache-file=config.cache'.
- Do not print messages saying which checks are being made. To
- suppress all normal output, redirect it to `/dev/null' (any error
- messages will still be shown).
- Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
-`configure' also accepts some other, not widely useful, options. Run
-`configure --help' for more details.
diff --git a/xorg-sched-yield-hack/ b/xorg-sched-yield-hack/
deleted file mode 100644
index a555417..0000000
--- a/xorg-sched-yield-hack/
+++ /dev/null
@@ -1,5 +0,0 @@
-SUBDIRS = src
- debian/changelog
diff --git a/xorg-sched-yield-hack/NEWS b/xorg-sched-yield-hack/NEWS
deleted file mode 100644
index e69de29..0000000
--- a/xorg-sched-yield-hack/NEWS
+++ /dev/null
diff --git a/xorg-sched-yield-hack/README b/xorg-sched-yield-hack/README
deleted file mode 100644
index dd12c75..0000000
--- a/xorg-sched-yield-hack/README
+++ /dev/null
@@ -1,4 +0,0 @@
-This package builds a that can be LD_PRELOADed before X to make X work.
-This ONLY works if X is not run setuid (i.e. is run as root)
-This however will work fine in most debian situations where it is launched by *dm
-The package contains debianization to install a diversion of /usr/X11R6/bin/X
diff --git a/xorg-sched-yield-hack/VERSION b/xorg-sched-yield-hack/VERSION
deleted file mode 100644
index f7f469a..0000000
--- a/xorg-sched-yield-hack/VERSION
+++ /dev/null
@@ -1,2 +0,0 @@
-#beryl version header
diff --git a/xorg-sched-yield-hack/ b/xorg-sched-yield-hack/
deleted file mode 100755
index 895f7cb..0000000
--- a/xorg-sched-yield-hack/
+++ /dev/null
@@ -1,15 +0,0 @@
-#! /bin/sh
-srcdir=`dirname $0`
-test -z "$srcdir" && srcdir=.
-cd $srcdir
-autoreconf -v --install || exit 1
-glib-gettextize --copy --force || exit 1
-cd $ORIGDIR || exit $?
-$srcdir/configure --enable-maintainer-mode "$@"
diff --git a/xorg-sched-yield-hack/ b/xorg-sched-yield-hack/
deleted file mode 100644
index 7271e9b..0000000
--- a/xorg-sched-yield-hack/
+++ /dev/null
@@ -1,24 +0,0 @@
-source $srcdir/VERSION
-#, [])
diff --git a/xorg-sched-yield-hack/debian/X b/xorg-sched-yield-hack/debian/X
deleted file mode 100644
index 124da9b..0000000
--- a/xorg-sched-yield-hack/debian/X
+++ /dev/null
@@ -1,2 +0,0 @@
-LD_PRELOAD=/usr/lib/ exec /usr/bin/X.schedreal "$@"
diff --git a/xorg-sched-yield-hack/debian/changelog b/xorg-sched-yield-hack/debian/changelog
deleted file mode 100644
index ac5ea2e..0000000
--- a/xorg-sched-yield-hack/debian/changelog
+++ /dev/null
@@ -1,12 +0,0 @@
-xorg-sched-yield-hack (0.1.0-1) dapper; urgency=low
- * Release version 0.1.0
- -- Quinn Storm <> Fri, 29 Sep 2006 10:06:40 -0400
-xorg-sched-yield-hack (0.0.1-0ubuntu1) edgy; urgency=low
- * Initial release
- -- Quinn Storm <> Sat, 23 Sep 2006 18:28:10 -0400
diff --git a/xorg-sched-yield-hack/debian/compat b/xorg-sched-yield-hack/debian/compat
deleted file mode 100644
index 7ed6ff8..0000000
--- a/xorg-sched-yield-hack/debian/compat
+++ /dev/null
@@ -1 +0,0 @@
diff --git a/xorg-sched-yield-hack/debian/control b/xorg-sched-yield-hack/debian/control
deleted file mode 100644
index a3ee5c9..0000000
--- a/xorg-sched-yield-hack/debian/control
+++ /dev/null
@@ -1,21 +0,0 @@
-Source: xorg-sched-yield-hack
-Priority: optional
-Maintainer: Quinn Storm <>
-Build-Depends: debhelper (>= 5), autotools-dev
-Standards-Version: 3.7.2
-Section: libs
-Package: libxorg-sched-yield-hack-dev
-Section: libdevel
-Architecture: any
-Depends: libxorg-sched-yield-hack0 (= ${Source-Version})
-Description: Static lib version of sched_yield hack
- This package is essentially useless
-Package: libxorg-sched-yield-hack0
-Section: libs
-Architecture: any
-Depends: ${misc:Depends}, xserver-xorg (>= 1:7.0.22)
-Description: Xorg sched_yield hack for nvidia speed
- Works around a bug in nvidia drivers that causes poor
- performance on xorg.
diff --git a/xorg-sched-yield-hack/debian/copyright b/xorg-sched-yield-hack/debian/copyright
deleted file mode 100644
index 92dfe05..0000000
--- a/xorg-sched-yield-hack/debian/copyright
+++ /dev/null
@@ -1,22 +0,0 @@
-This package was debianized by Quinn Storm <> on
-Sat, 23 Sep 2006 18:26:53 -0400.
-It was downloaded from <fill in http/ftp site>
-Upstream Author: <put author(s) name and email here>
-Copyright: <put the year(s) of the copyright, and the names of the
- copyright holder(s) here>
-<Put the license of the package here>
-The Debian packaging is (C) 2006, Quinn Storm <> and
-is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
-# Please also look if there are files or directories which have a
-# different copyright/license attached and list them here.
diff --git a/xorg-sched-yield-hack/debian/docs b/xorg-sched-yield-hack/debian/docs
deleted file mode 100644
index 50bd824..0000000
--- a/xorg-sched-yield-hack/debian/docs
+++ /dev/null
@@ -1,2 +0,0 @@
diff --git a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack-dev.dirs b/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack-dev.dirs
deleted file mode 100644
index 6845771..0000000
--- a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack-dev.dirs
+++ /dev/null
@@ -1 +0,0 @@
diff --git a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack-dev.install b/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack-dev.install
deleted file mode 100644
index d17b3c8..0000000
--- a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack-dev.install
+++ /dev/null
@@ -1,3 +0,0 @@
diff --git a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.dirs b/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.dirs
deleted file mode 100644
index 14f5b95..0000000
--- a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.dirs
+++ /dev/null
@@ -1,2 +0,0 @@
diff --git a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.install b/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.install
deleted file mode 100644
index eaafe21..0000000
--- a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.install
+++ /dev/null
@@ -1,2 +0,0 @@
diff --git a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.postrm b/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.postrm
deleted file mode 100755
index f780560..0000000
--- a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.postrm
+++ /dev/null
@@ -1,6 +0,0 @@
-if [ remove = "$1" ]
- dpkg-divert --package libxorg-sched-yield-hack0 --remove --rename --divert /usr/bin/X.schedreal /usr/bin/X
diff --git a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.preinst b/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.preinst
deleted file mode 100755
index 6021acb..0000000
--- a/xorg-sched-yield-hack/debian/libxorg-sched-yield-hack0.preinst
+++ /dev/null
@@ -1,6 +0,0 @@
-if [ install = "$1" ]
- dpkg-divert --package libxorg-sched-yield-hack0 --add --rename --divert /usr/bin/X.schedreal /usr/bin/X
diff --git a/xorg-sched-yield-hack/debian/rules b/xorg-sched-yield-hack/debian/rules
deleted file mode 100755
index 373526e..0000000
--- a/xorg-sched-yield-hack/debian/rules
+++ /dev/null
@@ -1,116 +0,0 @@
-#!/usr/bin/make -f
-# -*- makefile -*-
-# Sample debian/rules that uses debhelper.
-# This file was originally written by Joey Hess and Craig Small.
-# As a special exception, when this file is copied by dh-make into a
-# dh-make output file, you may use that output file without restriction.
-# This special exception was added by Craig Small in version 0.37 of dh-make.
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
-# These are used for cross-compiling and for saving the configure script
-# from having to guess our platform (since we know it already)
-DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-CFLAGS = -Wall -g
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
- CFLAGS += -O0
- CFLAGS += -O2
-# shared library versions, option 1
-# option 2, assuming the library is created as src/.libs/ or so
-#version=`ls src/.libs/lib*.so.* | \
-# awk '{if (match($$0,/[0-9]+\.[0-9]+\.[0-9]+$$/)) print substr($$0,RSTART)}'`
-#major=`ls src/.libs/lib*.so.* | \
-# awk '{if (match($$0,/\.so\.[0-9]+$$/)) print substr($$0,RSTART+4)}'`
-config.status: configure
- dh_testdir
- # Add here commands to configure the package.
- ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info CFLAGS="$(CFLAGS)" LDFLAGS="-Wl,-z,defs"
-build: build-stamp
-build-stamp: config.status
- dh_testdir
- # Add here commands to compile the package.
- $(MAKE)
- touch $@
- dh_testdir
- dh_testroot
- rm -f build-stamp
- # Add here commands to clean up after the build process.
- -$(MAKE) distclean
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
- cp -f /usr/share/misc/config.sub config.sub
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
- cp -f /usr/share/misc/config.guess config.guess
- dh_clean
-install: build
- dh_testdir
- dh_testroot
- dh_clean -k
- dh_installdirs
- # Add here commands to install the package into debian/tmp
- $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp
- mkdir -p $(CURDIR)/debian/tmp/usr/bin/
- install -m 0755 $(CURDIR)/debian/X $(CURDIR)/debian/tmp/usr/bin/X
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-# Build architecture-dependent files here.
-binary-arch: build install
- dh_testdir -a
- dh_testroot -a
- dh_installchangelogs ChangeLog -a
- dh_installdocs -a
- dh_installexamples -a
- dh_install -a
-# dh_installmenu
-# dh_installdebconf
-# dh_installlogrotate
-# dh_installemacsen
-# dh_installpam
-# dh_installmime
-# dh_installinit
-# dh_installcron
-# dh_installinfo
- dh_installman -a
- dh_link -a
- dh_strip -a
- dh_compress -a
- dh_fixperms -a
-# dh_perl
-# dh_python
- dh_makeshlibs -a
- dh_installdeb -a
-# dh_shlibdeps -a
- dh_gencontrol -a
- dh_md5sums -a
- dh_builddeb -a
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
diff --git a/xorg-sched-yield-hack/src/ b/xorg-sched-yield-hack/src/
deleted file mode 100644
index 831c18e..0000000
--- a/xorg-sched-yield-hack/src/
+++ /dev/null
@@ -1,2 +0,0 @@
-libxorg_sched_yield_hack_la_SOURCES = sched.c
diff --git a/xorg-sched-yield-hack/src/sched.c b/xorg-sched-yield-hack/src/sched.c
deleted file mode 100644
index 58d5f7b..0000000
--- a/xorg-sched-yield-hack/src/sched.c
+++ /dev/null
@@ -1 +0,0 @@
-int sched_yield() {return 0;}