mirror of
https://git.ari.lt/ari.lt/ari.lt.git
synced 2025-02-05 01:59:25 +01:00
33 lines
1.6 KiB
HTML
33 lines
1.6 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<html lang="en">
|
||
|
|
<head>
|
||
|
|
<meta charset="UTF-8">
|
||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
|
|
<title>Ari::web -> Blog</title>
|
||
|
|
|
||
|
|
<meta name="keywords" content="website webdev linux programming ari terminal dark blog javascript opensource free">
|
||
|
|
<meta name="description" content="Blog on 2021-10-27 02:01:13 EEST - Why I prefer source-based distros">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<div>
|
||
|
|
<h1>Why I prefer source-based distros</h1>
|
||
|
|
<p>2021-10-27 02:01:13 EEST | <a href="..">back</a> | <a href="/">home</a> | <a href="//github.com/TruncatedDinosour/website">git</a></p>
|
||
|
|
<hr/>
|
||
|
|
|
||
|
|
<p>Mainly because of tikarability, security and customisation, binary distros
|
||
|
|
don't give you as much control over your system customisability,
|
||
|
|
for example some software might be compiled with features you don't want
|
||
|
|
in the kernel and the source based one just requires some feature disabled
|
||
|
|
so you could get it, with binary ones you cannot. For example if you wanted to get
|
||
|
|
vim with no python support in source based distros you'd just disable it
|
||
|
|
where in binary ones you cannot and vise versa. I also like the customisation
|
||
|
|
of it because some packages won't work without systemD because of the
|
||
|
|
way they were built. Also if the binary built has some odd memory leak
|
||
|
|
you can't make it go away until the next update, but if you compile everything
|
||
|
|
then your binary will be unique. And few more things, like optimisation,
|
||
|
|
every binary you build even better if you pass certain flags to it.</p>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
<!-- this is automatically generated by scripts/add_blog -->
|