search

flathub / org.freedesktop.Sdk.Extension.texlive

7 stars 5 forks source link

Split extension into multiple profiles #157

Open axtloss opened 1 month ago

axtloss commented 1 month ago

The current texlive extension is very big, to the point that some projects don't use it simply because they don't want to bundle an >4gb extension. Since texlive already has profiles for installing, it would be useful to also split the extension into these profiles, which gives other apps more freedom with how much of texlive they wish to bundle.

My idea was to either provide three extensions, a full, basic and minimal one, but to give more flexibility it would also make sense to have each profile its own extension.

Since this would (probably) require a separate package for each extension, I would be happy to help with the setup and maintenance of these new layers (as from my understanding #35 was closed due to lack of "power" on doing it) .

jakobjakobson13 commented 1 month ago

@axtloss If you are willing to maintain it, you got my blessing.

axtloss commented 1 month ago

thanks! could you open an issue in the main flathub repo to add me as a maintainer to this extension?

jakobjakobson13 commented 1 month ago

You can open the issue yourself. That´s no problem.

However, it is not done by acquiring maintainer rights for this repository: As each flathub repository provides just one flatpak package, you have to open/create as many repositories as profiles you want to have. As a side question: Do you want to follow the selection of the texlive installer? (It works very differently from the flatpak approach as you choose one or multiple profiles and the installer loads the respective packages from ctan. This is not possible in a flatpak package as flatpak is immutable.) I wouldn´t know how do that elegantly without a massive load of maintaining.

Edit: The second paragraph is not correct, see the answers of hfiguiere.

hfiguiere commented 1 month ago

As each flathub repository provides just one flatpak package,

That's actually NOT true. The package could be split into module from one manifest. And the build would generate more than one binary package.

hfiguiere commented 1 month ago

You can open the issue yourself. That´s no problem.

I'm actually the one that said that the current maintainer should request this. We (the maintainer team) don't just arbitrarily give commit access.