SevenSpheres wrote: I'm still not sure how compiling/installing Celestia will work with two separate repositories.
Easy. You simply install 2 packages. Actually even before splitting we had 3 packages: 1st with binaries, 2nd with common files e.g. translations, shaders, etc and 3rd with data, e.g. textures, models and catalogues. We also have a meta-package which depends on all of them. Now I have all required files to build data package for Debian using the new repository. I just forget to contact munix9 to update his spec files for OpenSUSE and Markerz regarding macOS bundle.
SevenSpheres wrote: Two months later, CelestiaContent still hasn't been finalized and there are still data files in the main repository.
That's because we build packages only using the main repo still.
SevenSpheres wrote: It's unclear which files should go where; e.g. celestia.cfg is in the main repo, and so is the README file (although onetwothree is now saying that README should be in CelestiaContent!)
One README contains information regarding source code, another one is for data files. They are 2 quite different files. You can remove code related information from current README and copy it to data repository.
SevenSpheres wrote: Related to the above, data maintainers (e.g. me I guess) often have to make two pull requests to update things.
You may consider me rude, but you guys waste much more time discussing useless topics like who should have what colour in discord and here.