[elrepo-devel] We have fglrx packages and X does not behave. How to proceed ?

Manuel Wolfshant wolfy at nobugconsulting.ro
Wed Dec 23 09:25:35 EST 2015


On 12/23/2015 04:11 PM, Jamie Bainbridge wrote:
> On 23 December 2015 at 23:04, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote:
>> On 12/23/2015 02:57 PM, Ilyas Arinov wrote:
>>> Works for me with AMD APU 7850K, thanks for help.
>>
>>      You are welcome. But even if the current solution worked for now, with
>> the current state of my packages if/when RHEL releases an update to
>> xorg-x11-server-Xorg you will need to manually rename the culprit file again
>> or gdm will once again fail to start ( actually not gdm as you thought but X
>> , however this is irrelevant now).
>>
>>      I am looking into a real long term solution, not the AMD way which needs
>> reinstalling after each update of an OS package.
> To my knowledge there is no way around this within EPEL packaging
> guidelines, because fglrx intentionally overwrites the stock libglx.so
> like you say.
first of all, it does not overwrite but replaces. there is a fine 
difference here. second, afaict %triggerin should do it. but I wanted 
more opinions prior to playing with it. leaving aside that I also need 
some guinea pigs^W^W testers :)


>
> You could re-package xorg-x11-server-Xorg and override the EL package,
> however that would probably violate EPEL packaging guidelines because
> it interferes with a distro package.
I am not going to rebuild the packages provided by the OS under any 
circumstance


> Ubuntu have an fglrx package which survives updates. I know the kernel
> module rebuilds with DKMS, but how do they handle libglx.so? This
> might provide an idea you can use.
given that they also have control over the OS, they could have provided 
the necessary hooks in their .deb(s)



More information about the elrepo-devel mailing list