feat/versions #5512
Reference in New Issue
Block a user
Delete Branch "feat/versions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Add a stage to the build process that sparse clones deps and puts them in the required places.
This should make it much easier to keep track of vendored deps, and similar.
Solves #5426 and helps makes progress towards #4825
This pr moves almost all thirdparty deps from being vendored to being added by the build process.
This pr should be deployed on test and some cgi scripts tested before merge, there is some possibility of issues. But it should be minimal.
One thing: we manually mention the versions of things in https://fsfe.org/about/js-licences
I think we could make this automatic perhaps?
This pr atm does make us dependent on our sources being online for full builds. This is common, but perhaps not acceptable for us?
We could instead do one of the following:
State of deps
Moved
Could not move
Checklist
72f6766f74toea1c800083It might make sense to merge #5513 , which removes some unused dependencies, before this PR.
I have not contributed to fsfe-website nor do I know webdev well so I do not think I am the best suited to review this, especially with the diff being so large.
Cool, I pinged you as you created #5426
4c324aa9eeto735d63004cDo we need to? And what need people who work on the website need to install for building?
Sorry, that list of bullet points are all different options. So using nix is one option, but there are several others.
735d63004cto18330ab18418330ab184to4561ac40c04561ac40c0to323cd7fb97323cd7fb97tob2e370ff14Decided to move ahead with a POC implementation of using gitea mirrors of dependency repos.
Have to say, its very easy, seems like a great plan to me.
This pr now uses a bootstrap mirror at https://git.fsfe.org/delliott/bootstrap , just temporarily as a poc.
As we dont need to update often automatically (if ever) we could have a very low poll rate so as not to bother github, say once a week or even longer.
Main question I would have is where we put the mirrors? Probably system-hackers, we already have some mirrors there: https://git.fsfe.org/fsfe-system-hackers/?q=&mirror=1
Also might make sense to have a new namespace for mirrors of thirdparty software, keep it clear what is ours and what is external?
Any thoughts @tobiasd ?
de3baafaaato403a19731a403a19731ato64a66b1a24d4fba95851to054087c7f0054087c7f0tof9a1176a81413f8577b1to76fe7bfd56Discussed in the system hackers jourfix today.
The plan
--clean-cache). Should persist cache across ci runs.76fe7bfd56toe63a276694e81943688ftod4b3d98f28ced2213c70to2d4a99804c2d4a99804ctoe340a3878ee340a3878etoecf2715792ecf2715792to4b77db2b964b77db2b96to382d8cf9e8028300bd2dto7a73dbdd02e724947a15to4291d035f94291d035f9tob0547295f8b0547295f8to357ab1e552357ab1e552to957d7c7bc0957d7c7bc0to6767b898c56767b898c5to38ee28e35938ee28e359to6cc799f7c76cc799f7c7tod487680fe1d487680fe1to2896c78846WIP: feat/versionsto feat/versionsRight, this is now deployed on test to play with, and seems like it should be good to merge to me.
Might be no harm to test
perdiem.phpandreimbursement.phpon test before merge.They are internal tooling for employees, which I am not, so I cannot test them.
2896c78846to5e2ad0f4ab5e2ad0f4abtod0b45d9476d0b45d9476todc704799c2dc704799c2to26eee13d52@@ -0,0 +1,10 @@# SPDX-FileCopyrightText: Free Software Foundation Europe e.V. <https://fsfe.org>Does this file need to be executable?
No
Fixed