On Tue, Jun 27, 2017 at 06:14:10PM +0200, Floris wrote:
Op Tue, 27 Jun 2017 18:04:19 +0200 schreef David Wright <deblis@lionunicorn.co.uk>:On Tue 27 Jun 2017 at 17:37:53 (+0200), Floris wrote:Just wondering, why has the grub2-common package two update-grub files? One is just a symlink to the other ls -asl update-grub* 4 -rwxr-xr-x 1 root root 64 jun 23 12:35 update-grub 0 lrwxrwxrwx 1 root root 11 jun 23 14:47 update-grub2 -> update-grub If there are programs depending on update-grub2, a small transition might have been a nicer solution.Sorry, what's a "small transition" and what does it solve? Cheers, David.I think if there is a program depending on /usr/sbin/update-grub2 it shouldn't be difficult to update that program to /usr/sbin/update-grub. I known a symlink isn't "free-space-eating", but it looks more polished.
Actually, the preferred script is, apparently, update-grub2: * grub-*.install: Add update-grub2 stub. Packages providing /etc/grub.d/ scripts should invoke update-grub2 in both postinst and postrm (whenever it is found, of course). Source: <http://sources.debian.net/src/grub2/2.02~beta3-5/debian/changelog/?hl=4022#L4022> I also find 71 packages containing "update-grub". So it's not really a "small" transition. <https://codesearch.debian.net/search?q=update-grub> -- For more information, please reread.
Attachment:
signature.asc
Description: PGP signature