[Bug 248291] Review Request: libXNVCtrl - Library that provides the NV-CONTROL API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: libXNVCtrl -  Library that provides the NV-CONTROL API


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248291





------- Additional Comments From j.w.r.degoede@xxxxxx  2007-07-25 01:47 EST -------
(In reply to comment #4)
> OK, i've saw that you just have build libXNVCtrl but is there other libraries to
> build from the standard package or only the nvidia-settings binary is missing?
> 

There are no other libs AFAIK.

> About this don't you think that might be possible to build it also ?
> 

I don't want to be conflicting with the proprietary drivers from that other
repo, these do not contain this lib (as its linked staticly into
nvidea-settings),  but do contain nvidea-settings itself, and maybe a later version.

> For now i don't know how to bring nvidia users to uses this ? does your program
> will have a Requires (or BR) libXNVCtrl ?! Then this library will be bring on
> the system whereas the hardware may be not present...

Yes, gnome-applet-sensors will BR libXNVCtrl-devel, and then the build binary
will automatically require libXNVCtrl.so.0 . This is not a problem for non
nvidia driver users, this library just gives access to an X extension, just like
extensions as MITSHM, Xvideo and Xxf86dga. If the extension isn't available the
program will not use it and stay to function normally (except that it won't show
the temperature for any nvidia cards). So basicly with this lib, and an X-server
with the extension, nvidia card temp gets added as an additional feature. If the
server is missing the extension, then the app keeps functioning as before.

> The other way of doing this is to have Requires: libXNVCtrl from the proprietary
> nvidia driver, then does others problems will be able to dlopen this library to
> talk to the hardware... ?!
> 

As explained above this is not necessary.

> I think the first solution is the better, (maybe the two can be done...)
> 
> Anyway we may need to have for now (if only the proprietary drivers is
required...)
> ExclusiveArchs: %{ix86} x86_64
> 

This is not necessary either, on ppc the extension will simple not be there and
if nvidia does a ppc driver release, then things will start working without
needing a rebuild.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

_______________________________________________
Fedora-package-review mailing list
Fedora-package-review@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]