GNU bug report logs -
#52351
Is bad-packages-alist still relevant?
Previous Next
Reported by: Stefan Kangas <stefan <at> marxist.se>
Date: Tue, 7 Dec 2021 14:11:02 UTC
Severity: wishlist
Tags: patch
Fixed in version 29.1
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Severity: wishlist
Is bad-packages-alist still relevant now that we have package.el or
should it just be removed, as in the attached?
It was added in this commit and hasn't seen much use since, AFAICT:
commit a2603048ce283d22b37b35c9098d4583db244073
Author: Glenn Morris <rgm <at> gnu.org>
Date: Tue Aug 14 07:41:59 2007 +0000
(bad-packages-alist): New constant.
(bad-package-check): New function. Together, these two add
elements to `after-load-alist' to check for problematic external
packages.
The idea is to give warnings for incompatible external packages, but
this should be rather unusual these days, as most packages will be
installed with package.el and any incompatibilities are better handled
in that context. Furthermore, it seems to currently just warn about
really ancient versions of semantic and cua-mode.
IOW, not a bad idea at the time, but the passing of time has meant that
it's hard to see the relevance of the feature.
[0001-Remove-bad-packages-alist.patch (text/x-diff, attachment)]
This bug report was last modified 3 years and 149 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.