hakurei/internal/app/id.go, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/internal/app/id.go?h=develop2025-07-02T11:42:51Zcmd/hakurei: move to cmd2025-07-02T11:42:51ZOphestracat@gensokyo.uk2025-07-02T11:42:51Zurn:sha1:eb22a8bcc1ac03357d4073e5d3ed6d0ab5246a37
Having it at the project root never made sense since the "ego" name was deprecated. This change finally addresses it.
Signed-off-by: Ophestra <cat@gensokyo.uk>
app/instance: wrap internal implementation2025-04-12T04:56:41ZOphestracat@gensokyo.uk2025-04-12T04:56:41Zurn:sha1:6309469e933a31a300fbf16d8e77f48dcee402d3
This reduces the scope of the fst package, which was growing questionably large.
Signed-off-by: Ophestra <cat@gensokyo.uk>
fst: rename from fipc2024-12-18T06:50:46ZOphestra Umikercat@ophivana.moe2024-12-18T06:50:46Zurn:sha1:2f676c9d6e7baac289409cbcabde5b6e53b32ec3
Signed-off-by: Ophestra Umiker <cat@ophivana.moe>
app: move app ID to app struct2024-10-19T15:22:18ZOphestra Umikercat@ophivana.moe2024-10-19T15:07:48Zurn:sha1:ad0034b09aaa76aca478304518c1394ba292a619
App ID is inherent to App, and it makes no sense to generate it as part of the app sealing process.
Signed-off-by: Ophestra Umiker <cat@ophivana.moe>
app: clean up interactions and handle all application state and setup/teardown2024-09-21T16:15:39ZOphestra Umikercat@ophivana.moe2024-09-21T15:29:36Zurn:sha1:62cb8a91b603546314034ded1e9d6ddfbd6ef106
There was an earlier attempt of cleaning up the app package however it ended up creating even more of a mess and the code structure largely still looked like Ego with state setup scattered everywhere and a bunch of ugly hacks had to be implemented to keep track of all of them. In this commit the entire app package is rewritten to track everything that has to do with an app in one thread safe value.
In anticipation of the client/server split also made changes:
- Console messages are cleaned up to be consistent
- State tracking is fully rewritten to be cleaner and usable for multiple process and client/server
- Encapsulate errors to easier identify type of action causing the error as well as additional info
- System-level setup operations is grouped in a way that can be collectively committed/reverted
and gracefully handles errors returned by each operation
- Resource sharing is made more fine-grained with PID-scoped resources whenever possible,
a few remnants (X11, Wayland, PulseAudio) will be addressed when a generic proxy is available
- Application setup takes a JSON-friendly config struct and deterministically generates system setup operations
Signed-off-by: Ophestra Umiker <cat@ophivana.moe>