Open houseofsuns opened 2 years ago
I believed that this was fixed by this commit which was released with app-portage/gs-elpa-0.2.1.
Are there still remaining issues?
Ah, I missed that there is a repository with newer changes and installed the github version to hack on it.
I was annoyed by the fact that g-sorcery by default downloads sources during the build and was looking into providing a pregenerated overlay with distfile digests. My first attempt is at [1]. Do you think this is worthwile?
I would also be interested in reviving gs-pypi for an analogous overlay, but will have to dig around why it was phased out first.
Thinking about it, we should probably update the EAPI in g-sorcery and revert the change in gs-elpa. Otherwise there will be two places to keep track of.
I was annoyed by the fact that g-sorcery by default downloads sources during the build and was looking into providing a pregenerated overlay with distfile digests. My first attempt is at [1]. Do you think this is worthwile?
I have to talk to our infra team if hosting such a repo would be feasible. It only makes sense if it is updated automatically.
Thinking about it, we should probably update the EAPI in g-sorcery and revert the change in gs-elpa. Otherwise there will be two places to keep track of.
I concur.
I have to talk to our infra team if hosting such a repo would be feasible. It only makes sense if it is updated automatically.
My current idea is to add an update-tree command (so that each distfile needs to be fetched only once and does not need to be preserved for future use) to g-sorcery/gs-elpa and put that into a docker container which can be executed automatically. Hosting on Github works for now, but if this matures it would be great if it could be hosted on Gentoo systems.
This causes lots of errors for the generated ebuilds. I locally fixed this by bumping the default EAPI of g-sorcery to 8 and am currently looking whether this has any negative impacts.