todo
task
work-in-progress
task
/////////////////////////////////////////////////////////////////////////////// // AUTOGENERATED FILE! // // This file is automatically generated by SSS (Supreme Sexp System). // // Do not attempt to edit it directly, as your changes will be overwritten. // // Please refer to the relevant generation script or configuration instead. // ///////////////////////////////////////////////////////////////////////////////The tasks involved in this ticket include: - Identifying all files within the SSS project that are automatically generated. This might involve reviewing build scripts, code generation tools, and other development processes. - Modifying the generation scripts or tools to automatically prepend the warning header to the output files. This will likely require changes to the scripts themselves. - Ensuring the warning is correctly formatted for each file type (e.g., comment syntax for Lisp, Shell, Python, etc.). - Verifying that the warning is present in all generated files after the changes are implemented. - Documenting this convention for future development and maintenance. By implementing this clear AUTOGENERATED warning, we can prevent accidental manual modifications to generated files, which could lead to inconsistencies, errors, and difficulties in updating the system. This will contribute to a more robust and maintainable SSS codebase.
todo
bug
todo
story
todo
task
todo
task
todo
story
toys.whereis.socialtodo
task
todo
story
gettext
- Supporting multiple languages: Enabling the creation and inclusion of translation files for various languages.
- Providing mechanisms for users to select their preferred language.
Improved Logging:
To enhance debugging, troubleshooting, and system monitoring, this ticket also aims to improve the logging capabilities within SSS. This includes:
- Establishing a consistent logging format: Defining a clear and informative structure for log messages (e.g., timestamp, severity level, module/source, message).
- Implementing different logging levels: Allowing for filtering of log messages based on severity (e.g., debug, info, warning, error, critical).
- Defining log destinations: Configuring where log messages are written (e.g., system journal, dedicated log files).
- Ensuring comprehensive logging: Capturing relevant information during critical operations, errors, and significant system events.
By implementing robust i18n and logging, SSS will become more user-friendly for a global audience and easier to diagnose and maintain for both users and developers, contributing to a more polished and reliable "GNUrvana" experience.todo
task
dconf-service-type to enforce Nemo settings and others more declarativelytodo
task
dconf-service-type in the SSS configuration, we can:
- Declaratively specify default settings: Define the desired state of Nemo (e.g., default view, icon sizes, behavior) and others directly in our Guix configuration using Lisp.
- Ensure consistent settings: The dconf-service will enforce these settings across user profiles, promoting a consistent and predictable user experience.
- Improve reproducibility: The exact configuration of desktop components will be version-controlled and easily reproducible across different SSS installations.
- Enhance system management: Integrate desktop environment configuration more deeply into the Guix system management framework.
This approach aligns with SSS's goal of configuring all things via Lisp dialects when possible, promoting a more transparent, manageable, and ultimately more hackable desktop environment. It also opens the door to declaratively managing settings for other Dconf-managed applications in the future.todo
task
per-host.scm you can specify a list of strings, which represent packages you want to install for current host only, on top of SSS. This is good specially for device-specific drivers.
e.g.
;; Per host packages
(define sss-per-host-packages
( ;AMD non-free drivers
amd-microcode amdgpu-firmware
))
I dont think that will be enough for nvidia drivers though. It takes a lot of hoops to jump through to install nvidia-drivers!
https://wiki.systemcrafters.net/guix/nvidia/
You could start by adding a per-host.scm and sss-defaults.scm variable, e.g. sss-is-nvidia that is by default #f and for you will be #t, then hack directly into config.scm and wherever needed, by adding some cond statements, and conditionally applying the guide of system crafter
todo
task