Package Details: grub2-theme-archxion 1.0-6

Git Clone URL: https://aur.archlinux.org/grub2-theme-archxion.git (read-only, click to copy)
Package Base: grub2-theme-archxion
Description: Grub2 gfxmenu theme.
Upstream URL: https://github.com/Generator/Grub2-themes
Licenses: GPLv3
Submitter: American_Jesus
Maintainer: American_Jesus
Last Packager: American_Jesus
Votes: 161
Popularity: 0.000000
First Submitted: 2012-05-18 22:21 (UTC)
Last Updated: 2015-06-17 13:14 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4

dvzrv commented on 2012-05-21 13:17 (UTC)

hmm, generally I agree on that issue. On the other hand it will make copying a necessity each time the theme gets updated/installed. Argh... quandary

American_Jesus commented on 2012-05-19 01:37 (UTC)

Because some user may have a partition /boot part of the root, with limited space, this can result in installation failure. but it is a case to consider

dvzrv commented on 2012-05-19 00:22 (UTC)

Just a few questions about this package and grub2 theme packages in general: Why not directly install it to /boot/grub/themes/? Users with different install locations (probably the minority) could change the PKGBUILD, and users with standard install location (probably the majority) wouldn't have to copy the theme to the grub directory. I know there is this starfield theme in /usr/share/grub/themes that belongs to grub2-common, but wouldn't it make sense to directly put it to a folder that grub can reach (speaking of which: can grub actually reach other folders?... afaik it used to dislike splashimages not below /boot/grub/*)? Maybe these are stupid questions and they are ruled out by security issues/ pure logic? Not quite sure what the convention is here, but for me the copying kinda feels like a redundant thing to do.