Bug 175500 - sys-apps/915resolution ~x86-fbsd ebuild/patch & keyword request
|
Bug#:
175500
|
Product: Gentoo/Alt
|
Version: unspecified
|
Platform: All
|
|
OS/Version: FreeBSD
|
Status: CLOSED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: chutzpah@gentoo.org
|
Reported By: lavajoe@gentoo.org
|
|
Component: FreeBSD
|
|
|
URL:
|
|
Summary: sys-apps/915resolution ~x86-fbsd ebuild/patch & keyword request
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-04-21 21:27 0000
|
I've ported sys-apps/915resolution to Gentoo/FreeBSD, and attached are the new
ebuild files. I used similar methods and some code from a BSD port of
855resolution found here: http://www.sigusr1.org/~kurahone/misc-hacks/.
Now people with the Intel i810/i855/i915 (etc.) chips should be able to patch
their BIOS and get wide-screen resolution like 1280x768.
One note: -O2 breaks this build (the assembler part), and it's not really
needed anyway. I set CFLAGS to "" in the ebuild, which I have just heard is
not recommended (makes sense!). So really, we should filter the -O2 flag out
instead...
Created an attachment (id=116960) [details]
915resolution-0.5.3-r1.ebuild
Now use flag-o-matic to remove various flags, since optimization breaks the
assembly part of this build. This is more correct than hard-setting CFLAGS.
Created an attachment (id=117972) [details]
files/initd-r1
Fixed issue where returned error codes (from 915resolution program) will not be
remembered if not on last mode tried. Solution is to remember the last *bad*
(non-zero) error code returned and return that code. Please advise if it would
be better to return a fixed error code if one non-zero code is returned.
Also now insert separators between multiple modes in the log file for
readability.
Note: new initd file is named initd-r1 in new ebuild and in attachment. I have
changed the name of the ebuild back to reflect the old version number, so I am
unsure how to name this initd file; leaving as-is for now; please change as
appropriate when committing...
Port to ~x86-fbsd, bump version, keyword this arch only, fix init.d script.
Note to maintainer: please test on other archs and then re-add their keywords
(thanks!)
Re-opening, so we don't lose track that maintainer should test on other
archs...
Re-keyworded for x86, adding amd64 to CC as I don't have an amd64 machine with
an intel graphics card to test with
Should be able to close this now...
OK, closing. Thanks, everyone!