On 2 November 2013 at 09:55 Konstantinos wrote:
Starting with v0.6.4 (more specifically per this commit: http://commits.kde.org/kcm-grub2/f00845 ... b155be478b) any GRUB2 directory structure is supported, through the GRUB_FOO CMake cache variables as documented in the INSTALL file.
The Gentoo package (=kde-misc/kcm-grub2-0.6.4) does not make use of this new, flexible structure and won’t work properly (because GRUB_ENV and GRUB_MEMTEST are pointing to wrong files). /boot/grub/grub.cfg is a symlink to /boot/grub2/grub.cfg so GRUB_MENU won’t be affected, although it would be still pointing to the old file. You should poke your friendly package maintainer and ask for a better ebuild. To answer your second question, kcm-grub2 can work in Sabayon any time, as long as a proper package is created.
Starting with this version I will consider GRUB-naming-scheme-related bugs as packaging issues because it really is a pain in the ass to detect every different directory structure. The 2 most prominent directory structures are auto-detected (vanilla GRUB2 and the ’2′ suffix, as in grub2-foo-exe, /boot/grub2/ etc.) but for all the other cases, the packager should explicitly specify the GRUB2 directory structure of his distribution.
# tail -n 18 /usr/local/portage/kde-misc/kcm-grub2/kcm-grub2-0.6.4-r1.ebuild
$(cmake-utils_use_with packagekit QPackageKit)
$(cmake-utils_use_with imagemagick ImageMagick)
$(cmake-utils_use_with hwinfo HD)
Users browsing this forum: No registered users and 1 guest