Page MenuHomeSolus

Meta: Post-release blues
Open, HighPublic

Assigned To
Authored By
Aug 8 2017, 12:35 PM
Referenced Files
"Like" token, awarded by ToxicDragon."Like" token, awarded by Botanium."Like" token, awarded by miwilc."Love" token, awarded by Elvanex."Love" token, awarded by GladOSkar."Love" token, awarded by jalden."Like" token, awarded by Pilleo."Yellow Medal" token, awarded by curantes."Orange Medal" token, awarded by euoar."Party Time" token, awarded by ghishadow."Yellow Medal" token, awarded by m-delvalle."Yellow Medal" token, awarded by FriesischScott."Dat Boi" token, awarded by feskyde."Cup of Joe" token, awarded by mcritchlow."Dat Boi" token, awarded by Gabochuky."Like" token, awarded by K0baz."Cup of Joe" token, awarded by Craig-toyoracer."Like" token, awarded by blaz."Yellow Medal" token, awarded by kyrios123.


TODO: Prioritize this list JIRA style.

Tracking task for stuff to fix after the next release:

Super High Priority (This is post ferryd deployment)

  • ferryd. Seriously.
  • Replace broken-ass-third-party ! (@ikey attending Ubuntu Rally in NYC to work on this, end of September 2017)
  • @ikey: Document stateless, best approaches, IRC tribal knowledge on Help Center

Post ferryd high-priority items here (Might need de-duping and organising!)

  • Rebase on new systemd
  • Resolve providers of mozjs and spidermonkey @ikey
  • Re-enable Wayland and test
  • Sort out samba and Nautilus (This is @JoshStrobl's task, no touchy!)
  • Swap out goofiboot for upstream systemd-boot and lose some technical debt
  • Reintroduce libgudev to assist in the migration, consider base-level hard dep to ensure it gets in on upgrade
  • Dropkick old + crusty library providers, i.e "webkit1", consolidate them (@joebonrichie is working on moving things to webkit2)
  • Draw up a formal sync cycle (i.e. how to remain unblocked and maintain high velocity)
  • Evaluate toolchain options (sane toolchain, and ensuring Clang works as well as GCC at minimum)
  • Automate security advisories, integrate Solus in upstream discussion points
  • Support firmware capsule updates (track upstream at clr-boot-manager repository)
  • Add a lot more testing to Solus, both at the package level %make check and at the QA pipeline level. Track these metrics (perf, use case, etc)
  • Ensure package "lintian". i.e. all packages should use particular standards and filesystem layouts. Document it.
  • Expand solbuild- allowing sandboxed dbus, X11, etc, to allow PGO, test suites and such
  • Produce a solid stateless definition within the context of Solus- provide management tooling for this too. Undocumented hard to use stateless isn't much help.
  • Evaluate stateless system account options, i.e. nss-altfiles, etc (We're fine with systemd-sysusers for now)
  • Convert at least 98% of all Solus packages to our ypkg build format.
  • Centralise actionable scripts for drivers and providers in mesalib, xorg-server and nvidia-* to kernel-integration package (replaced with usysconf)
  • Add snapd- instead of backing a single format we'll support both Flatpak and Snaps and maximize user choice. This also ensures Solus is not tied to any single provider. (Note: Flatpak is no longer the universal app solution we initially agreed to adopt, rather, it is a meta-distro)
  • Add analysis of image and build artifacts to ensure packages and images are consistent with "the Solus way" (FHS, build flags, RELRO, canary, etc)
  • eopkg-> sol (next gen system software/framework management)
  • First-class hybrid GPU support (i.e. linux-driver-management, Optimus, and dynamic GPU switching, with OS/desktop integration)
  • Implement a TLP alternative (so people get better battery life without the risk of their drive randomly unmounting or wireless being a spud)
  • Dramatically increase hardware support no matter what it takes (i.e. "dodgy" printers)
  • KDE/Plasma stabilization
  • OEM installer mode
  • Support AppArmor LSM
  • Fix conformance checking for licenses in packages
  • (EVENTUALLY) Switch eopkg and ypkg to clang by default, allow disabling Clang on a per-package-basis (Supported this for a long time, just flip the default now)

Super duper low priority

  • X stack update (mostly just the server 1.19+ & driver rebuilds) Note: We tried this with 1.19.4 and will at a future date.


Solus is partly stateless in some places, but not enough. It also relies on a partial definition from Clear Linux, but has never bothered to define it further within the context of Solus.
It is also true that new users may be confused by the stateless approach taken by some packages. Thus, an OS-wide stateless policy will be defined, which all packages must then
obey. Additionally, it should be done so in a fashion that would enable an automated tool to manage policy-compliant stateless packages "all in one shop". Said tool should also support
exporting a system diff and the application of said diffs for management and deployment. The tool is less important than actually documenting the changes and having them stateless.
If such a tool is built, it should be done so in a completely agnostic fashion.

Refined mission statement

If you can stomach the marketing spiel- this is heart of Solus:

A safe and reliable vehicle to guide, guard and enable the user's journey through a shifting tech world, to their destination and beyond.

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
ikey changed the status of subtask T4524: Make repos go fastly from Open to In Progress.Sep 20 2017, 3:09 AM

About how many hours of sleep did that set you back? :P

Jesus you don't even wanna know. It's 11:35AM here. All nighter. But ferryd is now actively serving Solus!

Not all superheroes wear capes, some of them have bags under their eyes instead ;)

@W-Floyd And some of them deserve to go out for a pint this evening, ain't that right @ikey =)

All this work for only 2 days...

of course it's a site...

Now that Make repos go fastly is resolved, you can mark "Draw up a formal sync cycle (i.e. how to remain unblocked and maintain high velocity)" as done right?

Apart from that, we could add the Silent boot subtask here and add it too as another TODO.

And maybe we could add too Firmware update in clr-boot-manager and gcc/llwm updates?

Now that Make repos go fastly is resolved, you can mark "Draw up a formal sync cycle (i.e. how to remain unblocked and maintain high velocity)" as done right?

Oops, fixed, thanks! GCC will not be updated to the same version again (Hint: It's broken :P) we're waiting for 7.3 because it won't brick glibc x86 ABI.

So do you mean fw capsule updates managed by clr-boot-manager? Sounds good to me tbh - so we should raise this on the upstream clr-boot-manager repo. Weird me not
being the upstream anymore :P

In T4235#83002, @ikey wrote:

So do you mean fw capsule updates managed by clr-boot-manager? Sounds good to me tbh - so we should raise this on the upstream clr-boot-manager repo. Weird me not
being the upstream anymore :P

Yeah, like allowing for example fwupd updating them or just figuring out another way

Yea, I'll poke this on cbm repo now

JoshStrobl updated the task description. (Show Details)
JoshStrobl added a subscriber: DataDrake.

New systemd 235 now in unstable

Will systemd-boot be enabled for Solus 4 or is that further down the road?

Ehm not sure atm. If I enable it now we're just gonna have stray/dead goofiboot sitting on the ESP, but I honestly think there's nothing we can do about that :3

Oh. It's only 84k. OK well thats hardly earth shattering

Ehh I'd be more than happy to write up a little guide to remove it if you want. I've done it before. Then you could just put it up somewhere for people to run if they want.

It won't need removing, see my last commit there. We'll handle a full transition when we can do the EFI var manipulation. For now, its harmless for the goofiboot
stub to remain there (and is good for recovery anyway.)

Yea sorry didn't see the other posts. Balancing attention between finals review session and this chain haha

:D Good luck with finals :)

oly removed a subscriber: oly.
oly added a subscriber: oly.

I need to go through this and split things out as appropriate.