this post was submitted on 05 Nov 2023
114 points (98.3% liked)
Open Source
31175 readers
158 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Looking at it, I see the following...
GitLab's deps:
Forgejo deps:
I am missing something?
I assume that's to build from source.
The times I've installed GitLab it's been a case of
dnf install https://...
. The rest gets dragged in automatically.Well, this way they could install dependencies anyway just automatically, so you don't see them unless you read before accepting the installation. I still can read this:
And then:
So they do some magic here, the script just installs the repository, so I can't see exactly any dependency they are currently using.
Probably Forgejo/Gitea also uses such dependencies, but their Go counterparts which are statically built into the server binary.
If resource efficiency only depended on that, Gitlab would be more efficient with memory because of this. We all know that's not the case, I just said it as a comparison.
This also means that while Forgejo/Gitea depends less on your system installation, it also wont benefit from updated dependency packages.
If they maintain the binary properly, could cause less issues with dependencies compatibility, so it's less pain for the DevOps team, like a container image, just pull the new image and done.