Any updates on 'sol' ?

prateekmedia

It has been raised in many old discussions and some blog posts too that eopkg will eventually be replaced by 'sol', but I can't find any reference in the latest discussions and posts.

So is there any progress of the sol package manager?

George

prateekmedia if I remember correctly, then @DataDrake needs to do ferryd (done), ypkg and only then sol, after @JoshStrobl make a new software-center. It can be considered an official roadmap of Solus

Harvey

If there was something more to say, they would say it. ferryd among many other things continues to be worked on.

stalebrim

If you install aisleriot package you get sol 😀

WetGeek

stalebrim If you install aisleriot package you get sol

Yeah, you get 100+ sols!

DataDrake

George ferryd is not done.

DataDrake

George Strictly speaking, ypkg3 isn't a blocker for writing sol, but it will have a greater impact on the day-to-day maintenance efforts. It's also a comparatively smaller project, so I'd like to finish it earlier rather than later. sol is a lot more involved and will need significantly more attention to detail, optimization, and testing. Because I'm super busy with PhD stuff this semester, it's likely that it's looking more like ypkg3 (spring) --> ferryd (summer) --> sol (fall start). There are a few other smaller projects that I'll be tackling along the way, but those mainly affect the Core Team, not other users.

George It can be considered an official roadmap of Solus

No. There is no official roadmap at the moment.

George

DataDrake ooh, ok i'm wrong, but other is right?

JoshStrobl

I will be working on the UX, a generic provider class, and flatpak and snap providers for the new Software Center once my existing backlog of Solus items, as well as some current contract work, is finished. That way, once sol is done, the sol provider can be implemented and we can begin testing the new SC.

No ETAs as always.

STiAT

JoshStrobl that's sounds great, especially the generic provider class with providers for different systems. Implementation, Limits and the UI to that are a challenge, but I'm sure you have a vision on what you want there (either the provider getting their own "space" as 3rd party, maybe even getting their own repo settings as in flatpak, or integrated in the main "search" view differentiating there between solus packages/flatpaks/snaps), and only providing like snaps with snapcraft and flatpak with flathub without user-config options (makes no sense for snaps, but for flatpaks maybe).

I'd actually be interested in helping out on implementing the flatpak provider once the ground work is laid, the generic class needs to be coherent with the UI and general implementation vision, so is in best hands with you (once you can find time .. which probably is the hardest challenge).

// G