[Slackbuilds-users] Size limit for vendored dependencies
Willy Sudiarto Raharjo
willysr at slackbuilds.org
Tue Aug 12 12:57:05 UTC 2025
> I took upon myself an endeavor to write a script that builds network/element-desktop from source. After many hours I succeeded to build it offline. Some vendoring optimization later I ended up with a vendored-sources tarball that's 700-900 Mb, depending on compression method (three layers of yarn, a layer of cargo and a couple of pre-built packages, most of it is already compressed so any compression only saves ≈10-20%). That's not an issue for SBo as no source is hosted here and all of that would be downloaded anyway even without vendoring, however it is a potential issue for a comminity infrastructure, namely slackware.uk which caches all source tarballs.
>
> What would be a sensible size limit for vendoring dependencies before going "screw it, just enable network access"?
you should ask Tadgy for that, but i think he has enough space for 900MB
considering he also host cumulative repo which uses more size.
--
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250812/068c6bea/attachment.asc>
More information about the SlackBuilds-users
mailing list