Celestia Forums

Quite long time ago we (dev team) decided to split code and content into separate repositories.

Main point for this are:

• Smaller application updates, users don't need to download several dozens of megabytes when only application was changed.
• More frequent content updates for all actual versions.
• Smaller repository size: 1.7 and 1.6.2 live in two different branches, so to update both we need duplicate files in both branches. In a separate repo we'll keep data only once.
• Potentionally better integration with other Celestia-related projects like Celestia Origin.

According with I created a new repository https://github.com/CelestiaProject/CelestiaContent. It contains copy of data, extras, extras-standard, images, models and textures directories. Since today we stop accepting content-related changes to the main repository.

We also looking for volunteers to maintain this new repository. The most important task from my PoV is to replace non-free files with files with free licenses (see here).

I could definitely help, but not with making new, free textures (besides, Askaniy was going to do that). I had suggested making an issue to track data updates; I guess I'll do that in this repository?

How will compiling and installing work with two different repositories? Also, will the new repository retain the history of the data files?

SevenSpheres wrote:I guess I'll do that in this repository?

feel free

LukeCEL wrote:How will compiling and installing work with two different repositories?

We will produce 2 installation packages: one for the application and another one for data. Alternatively we can use content repo as git submodule (as we do with some 3rd party dependencies) and produce a single package for cases when several packages are not possible like macOS bundle.

LukeCEL wrote:Also, will the new repository retain the history of the data files?

Hmm, I just copied them, maybe it worth to recreate using the current repo and remove code directories.

onetwothree wrote:maybe it worth to recreate using the current repo and remove code directories.

I think that would be a good idea.

Could some people not on the Celestia Development Team (e.g. Askaniy, LukeCEL, and myself) be given write access to this repository? That would probably make things easier.

SevenSpheres wrote:Could some people not on the Celestia Development Team (e.g. Askaniy, LukeCEL, and myself) be given write access to this repository? That would probably make things easier.

Well, the devs could use some extra help. What do you say, devs?

Done.

Since the CelestiaContent repository is taking a very long time to be finalized, I decided to just go ahead and make some pull requests there. The issues with these PRs are making me think that splitting the repositories was a bad idea that creates more problems than it solves.