Re: [dev] Linux distros that don't suck too too much

From: Hans Ginzel <hans_AT_matfyz.cz>
Date: Thu, 12 May 2016 17:36:44 +0200

On Thu, May 12, 2016 at 07:42:26AM -0700, Charlie Kester wrote:
>Package systems are both a symptom and a cause of bloat. They only
>exist because most software, along with its metastasizing dependencies,
>is a pain in the ass to compile.
>
>The correct solution isn't hiding those problems with a package
>manager, but to avoid those dependencies and the bloat in
>individual programs by following suckless principles in the first place.

Which concrete principle do you mean, please?

Copying the “shared/same code” into each program?
But how to maintain updates of such code, e.g. security update?

The code could be in a library. But if you want to dismiss
packages/dependencies it is necessary to link statically.
But how to determinate which all programs to recompile
in case of (security) update? Grepping header files?

And in multiuser environments, where each user compile it's programms,
because of the “Configuration/customization in header file” principle,
how does the maintainer force every user to recompile
it's appropriate set of programms in case of (security) update
of a library code? Is such system maintainable, please?

Kind regards,
Hans

PS: Think about the Heartbleed bug in openssl for example.
Received on Thu May 12 2016 - 17:36:44 CEST