[Slackbuilds-users] nvidia-kernel vs. xorg.conf

[emmel]

On Wed, Jul 27, 2011 at 02:22:23AM +0200, Thomas Morper wrote:
> Hello there,
> 
> Recently, a new bit of code, that will put an xorg.conf.d/device.conf to
> the resulting package, has been added to the nvidia-kernel SlackBuild.
> 
> While this is convenient for most first time installs, it's less
> convenient when updating, because the hardcoded device.conf will
> overwrite any user-made changes and will clash with certain multi-head
> setups.
> 
> I think I'd rather have the device.conf in the doc-directory and a hint
> in the README. Still convenient for first-time installs, but won't break
> existing setups. What do you think?

Short answer:

No.

Long answer:

You are thinking the wrong way. The package ought to work right out of
the box, so the config should be included. This will override changes
made by the user, but everyone who knows what they are doing - and quite
frankly, if you edit the Xorg.conf, you should - will be able to fix
this. Once.
Remember that /etc/X11/xorg.conf.d overrides /usr/share/X11/xorg.conf.d.
So you should mention in the README, that this package now uses the
conf.d style in order to let people know that there might be trouble
updating, but not overcomplicate things. Adding it as a .new file
doesn't really make sense, as the package installed version should be
outside /etc.

Just my two cents.
-- 
GPG signed
Fingerprint: 60B4 D8E3 9617 900C 6726  168F D677 5AAD D40F CCE7
Certserver : hkp://pgp.mit.edu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110729/2b0736b1/attachment.asc>