Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Why break a single source package into many small packages?
Why break a single source package into many small packages?
Can anyone shed some light on why Debian breaks a single source package into many small packages? For example, Debian separates development files and actual executable/libraries; it also sometimes separates documents into an individual package (gcc-doc).
Re: Why break a single source package into many small packag
40 years of UNIXThe UNIX philosophy is “Do one thing, and do it well.”
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: Why break a single source package into many small packag
To allow users to strip down their systems as much as possible and save space, this is mainly applicable to embedded systems these days though.xuhdev wrote:Can anyone shed some light on why Debian breaks a single source package into many small packages?
Alpine Linux goes a step further — with separate -doc packages for the man pages and suchlike — and this allows it a very small footprint indeed.
By contrast, Arch Linux mashes all the header libraries in with the packages (hence no -dev packages) so Arch boxen tend to be more bloated even if the actual number of installed packages is significantly lower.
deadbang