Context Navigation

Changes between Initial Version and Version 5 of Ticket #30914

Ticket #30914
- Property Cc jhpalmieri fbissey isuruf arojas dimpase slelievre added
- Property Summary changed from Generate sage/share files in sage/setup.py? to Meta-ticket: Create upstream repositories, pip-installable packages for database packages

-                      initial
+                      v5
+Problem: While working on #30371, I noticed that most files in `local/share` are more or less static, but are generated during `make`.
+I was wondering how to streamline this process a bit in order to make modularization easier, and to make it possible to install sagelib in different venv and without a previous run of `bootstrap`/`make`.
+The Sage distribution contains a number of "database packages", many of which do not seem to have a "real upstream" (or installation procedures other than our scripts in build/pkgs).
+Options that I see:
+. Checkin the current version of these files (at least the almost static databases etc) in say `src/share`. Then they only need to be generated anew for update due to changes upstream. So one can remove the corresponding sage packages from the `make` pipeline.
+We transform them into pip-installable packages and publish them to PyPI so that they can be installed using standard Python tools (and become Python dependencies of sagelib).
 . Publish these dependencies to pypi, and install them to the current venv using requirements.txt and/or pipfile.
+For those that do not have a real upstream, we create separate git repositories in github.com/sagemath/ to serve as new upstream.
+. Generate these files during a call of `src/setup.py`, and include them in this way in the current venv.
+List of packages/tickets:
+Any other ideas/preferences about how to handle these files?
+TBD