Volker Armin Hemmann wrote:
> remove the blocker? the current nvidia-drivers work fine, if you 
> add -ignoreAbi to your X-start script (like kdm conf).
>   


The problem is that any nvidia-driver is the blocker to
xorg-server-1.4-r1.

royw-gentoo portage # emerge -uDNpv world

These are the packages that would be merged, in order:

Calculating world dependencies... done!
[ebuild  N    ] x11-libs/pixman-0.9.5  USE="-debug" 0 kB
[ebuild     U ] x11-base/xorg-server-1.4-r1 [1.3.0.0] USE="dri hal%*
ipv6 nptl sdl xorg xprint -3dfx -debug -dmx -kdrive -minimal"
INPUT_DEVICES="keyboard mouse -acecad -aiptek -calcomp -citron
-digitaledge -dmc -dynapro -elo2300 -elographics -evdev -fpit -hyperpen
-jamstudio -joystick -magellan -microtouch -mutouch -palmax -penmount
-spaceorb -summa -synaptics -tek4957 -ur98 -vmmouse -void -wacom"
VIDEO_CARDS="nv vesa vmware -amd% -apm -ark -chips -cirrus -cyrix -dummy
-epson -fbdev -glint -i128 -i740 -i810 (-impact) -imstt -mach64 -mga
-neomagic (-newport) -nsc -r128 -radeon -rendition -s3 -s3virge -savage
-siliconmotion -sis -sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6)
(-sunffb) (-sunleo) (-suntcx) -tdfx -tga -trident -tseng -v4l
-vermilion% -vga -via -voodoo -xgi% (-fglrx%) (-nvidia%*)" 0 kB
[ebuild     U ] x11-drivers/xf86-input-keyboard-1.2.2 [1.1.1-r1]
USE="-debug" 0 kB
[ebuild     U ] x11-base/xorg-x11-7.3 [7.2] 0 kB
[blocks B     ] x11-drivers/nvidia-drivers (is blocking
x11-base/xorg-server-1.4-r1)

Total: 4 packages (3 upgrades, 1 new, 1 block), Size of downloads: 0 kB


Looking in the xorg-server-1.4-r1.ebuild:

  IUSE_VIDEO_CARDS="

  [snip]

  #       video_cards_fglrx
  #       video_cards_nvidia"

  [snip]

  PDEPEND="
          xorg? (

  [snip]
 
                 !x11-drivers/nvidia-drivers
                  !x11-drivers/ati-drivers
          )"
  #               video_cards_nvidia? ( x11-drivers/nvidia-drivers )
  #               video_cards_fglrx? ( >=x11-drivers/ati-drivers-8.37.6 )


I recall reading that the xserver team changed their
release policy to not hold up releases for proprietary
drivers (same as the kernel team).  So this is as expected.

I was just hoping someone would have a more elegant
management solution for handling the new situation.


Thank you,
Roy

-- 
[EMAIL PROTECTED] mailing list

Reply via email to