People would then see that messages if they want looking to README.gentoo file also. These are the messages that could use this eclass, I can do the changes myself if you let me do: elog "You must be in the video group to use the NVIDIA device" elog "For more info, read the docs at" elog "http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap3_sect6" elog elog "This ebuild installs a kernel module and X driver. Both must" elog "match explicitly in their version. This means, if you restart" elog "X, you must modprobe -r nvidia before starting it back up" elog elog "To use the NVIDIA GLX, run \"eselect opengl set nvidia\"" elog elog "To use the NVIDIA CUDA/OpenCL, run \"eselect opencl set nvidia\"" elog elog "NVIDIA has requested that any bug reports submitted have the" elog "output of /opt/bin/nvidia-bug-report.sh included." elog if ! use X; then elog "You have elected to not install the X.org driver. Along with" elog "this the OpenGL libraries and VDPAU libraries were not" elog "installed. Additionally, once the driver is loaded your card" elog "and fan will run at max speed which may not be desirable." elog "Use the 'nvidia-smi' init script to have your card and fan" elog "speed scale appropriately." elog fi if ! use tools; then elog "USE=tools controls whether the nvidia-settings application" elog "is installed. If you would like to use it, enable that" elog "flag and re-emerge this ebuild. Optionally you can install" elog "media-video/nvidia-settings" elog fi Reproducible: Always
Why I need to read the same messages always in my summary.log?
I can do this myself if you let me do :)
Created attachment 360708 [details, diff] 1.patch
Comment on attachment 360708 [details, diff] 1.patch Ok, that looks promising. But instead of repeating these messages in every ebuild, I'd rather migrate them to nvidia-driver.eclass...
(In reply to Jeroen Roovers from comment #4) > Comment on attachment 360708 [details, diff] [details, diff] > 1.patch > > Ok, that looks promising. But instead of repeating these messages in every > ebuild, I'd rather migrate them to nvidia-driver.eclass... I am unsure about that: nvidia-driver.eclass doesn't take care of src_install neither pkg_postinst and, then, create and print doc calls should be kept in ebuilds. I guess you refer to setting DOC_CONTENTS in eclass?
(In reply to Pacho Ramos from comment #5) > I am unsure about that: nvidia-driver.eclass doesn't take care of > src_install neither pkg_postinst and, then, create and print doc calls > should be kept in ebuilds. I guess you refer to setting DOC_CONTENTS in > eclass? Yes, just the inherit and the messages in the eclass, and call readme.gentoo_create_doc in pkg_postinst() in the ebuilds, I should think.
Created attachment 360710 [details, diff] 1.patch This is the change needed for eclass, just tested it work ok (after dropping that same lines from the ebuild)
(In reply to Pacho Ramos from comment #7) > Created attachment 360710 [details, diff] [details, diff] > 1.patch > > This is the change needed for eclass, just tested it work ok (after dropping > that same lines from the ebuild) Yes, I have that in place already (but not committed yet) and I am working on the ebuilds...
Fixed. Thanks for the suggested changes/patches.
