3 ms·
HEADLINE: Full audit of what's in "standard" and "important" DESCRIPTION: There have been numerous detailed analyses posted to debian-devel that go through eve
by JoshTriplett 9y ago
HEADLINE: Full audit of what's in "standard" and "important"
DESCRIPTION: There have been numerous detailed analyses posted to debian-devel that go through every package in standard and important and list out which ones shouldn't be. However, actual changes have only ever been made here on a point-by-point basis. (I've managed to get a dozen or so packages downgraded to "optional" and out of the default install by filing bugs and convincing the maintainer.) I'd really like to see a systematic review that results in a large number of packages moved to "optional".
This would include downgrading all the libraries that are only there because things depending on them are (no longer something enforced by policy). And among other things, this may also require developing support in the default desktop environment for displaying notifications for urgent log messages, the way the console does for kernel messages. (And the console should do so for urgent non-kernel messages, too.)
DISTRIBUTION: Start with unstable early in the development cycle, so that people can test it out with a d-i install or debootstrap install of unstable.
- voltagex_ 9y agoI'm interested in this - does this mean the size of a default install becomes smaller? Is there anywhere to read more about this?
- guillemj 9y agoPlease check https://wiki.debian.org/BusterPriorityRequalification https://wiki.debian.org/BusterPriorityRequalification, https://wiki.debian.org/Proposals/EssentialOnDiet https://wiki.debian.org/Proposals/EssentialOnDiet and https://wiki.debian.org/Teams/Dpkg/Spec/ImportantField https://wiki.debian.org/Teams/Dpkg/Spec/ImportantField. We should discuss some of this at some point on debian-devel.