The file references README.gz, but the default is README.bz2 in recent Portage versions. Also the user may have set a different compressor via PORTAGE_COMPRESS in make.conf.
Can I just use $PORTAGE_COMPRESS to determine this in the ebuild?
Currently PORTAGE_COMPRESS is unset in the environment, when not set by the user. Also we'd need to test if PORTAGE_COMPRESS equals gzip || 7zip || ... then come up with the extension and modify every single ebuild accordingly when a new compresser gets supported. Best would be, if Portage would provide PORTAGE_COMPRESS_EXT, automatically set to the correct value.
re-assigning to Portage since there's no way to fix this bug currently because of the way Portage does things.
Why can't you just refer to README? I it's quite annoying that you have to update your config files because of the README path for every new version of nvidia-drivers.
All the update systems ignore that change since the change is made within a comment.
(In reply to comment #5) > All the update systems ignore that change since the change is made within a > comment. > For dispatch-conf you can at least configure whether to automatically do it or not. I usually prefer to read the changes.
(In reply to comment #3) > re-assigning to Portage since there's no way to fix this bug currently because > of the way Portage does things. You can use $(ecompress --suffix), but why on earth is this important? Can't people use brain instead of requesting totally pointless hacking with README suffix? Anyway, this is a dupe. *** This bug has been marked as a duplicate of bug 169772 ***
