[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: c96-3465667488.png (257 KB, 540x511)
257 KB
257 KB PNG
>libc updates
>99% of all packages need an update
fucking unbelievable
why is libc coded by spergs with no practical experience/ gnome developers ?

MSVCRT/UCRT superior
i want MSVCRT/UCRT replacing libc NOW.
>>
>>106768364
>99% of all packages need an update
Is this the power of flatpaks?
>>
>>106768364
Ask Microsoft to license it as mit at least.
>>
>>106768364
not libc but the way linux uses that shit like it's still 1970
>>
>>106768378
>Is this the power of flatpaks?
No contrary flatpaks are supposed to fix it and they do, native packaging has this issue, but no one is going to adopt flatpaks or any universal packaging format so the hope is for a better C library.
>>
>>106768389
>not libc but the way linux uses that shit like it's still 1970
Bullshit, libc is the number 1 biggest problem and number 2 is adopting unix standards and not getting rid of them since a good chuck of it is outdated.
>>
>>106768409
why libc if msvcr has versions too but windows handle them properly
>>
>>106768364
Never seen that on Gentoo. Is this behavior typical for binary-based distros?
>>
>>106768392
false
all flatpaks need an update if libc is updated
traditional distros, you only have to update libc and everything benefits automatically
every flatpak has its own libc. so every flatpak needs to be updated to get it



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.