-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation out of date #284
Comments
Hi @Narice Thank you for the report and apologies for the inconvenience. After having incorporated the new digga library & API on the road to a 1.0, we should scramble and update the docs for the devos template asap, which have become somewhat stale not only with respect to suites.
The separation was made since we plan to add different configuration builders for different systems in the future. One such example would be a Such config subsystems would need their own set of API semantica and since there is already a slight difference for hm configs (no Suites are moved to the flake.nix because they where such a "shallow" concept and should be visible already in a repo's ebtry point. Tink "table of contents". In that move, it made sense to split the ones for home manager and nixos. For interested parties who stumble over this, there is also #283 which is intended to specifically answer the most pressing questions while migrating. |
Alright thanks for the quick response!
I'm using nix unstable for the flakes capabilities (currently on NixOS) |
No rules. As long as you put it forth, the way you like, that's fine. 👍
I think finishing off the rework will be a matter of a couple of more days, only. So In this case, patience until we fix this might ne the best course of action. It shouldn't take long, we are highly commited to make this a nice experience for everyone. Thanks for reporting! |
I remember updating this and reading the docs in core and the doc website, they indicate that suites are in the flake.nix. Is there some line I'm missing that wasn't updated?
This is a good request. For the most part we do follow this rule. But sometimes there are portions of the doc that we might miss. So thanks for reporting this, lets try and get the doc completely up to date.
Keep in mind that devos goes through versions. And its common to see devos repositories that use a different version from core. I can actually reproduce your issue! I thought it happened to me because of a change I made in my repository. Your comment just helped me realize what it actually was. |
I opened a dedicated issue for the |
Oh! Thank you very much for the feedback and your answers
I didn't include the trace for this one as it is too long |
Wow that is a very odd error. It does work for me. That could be a nix problem. Or maybe its because of our use of sub-flaking - guess based on the |
If you execute the command in an empty directory, does it work? |
Yeah it still works then for me. Also can you try out #286, that should fix your original issue. |
Alright, thanks! My guess is that I don't have the proper version of nix unstable or something like that ;) |
with the new digga, the iso page is out of date:
it should be:
EDIT: fixed comprehension mistake |
The documentation of suites is out of date for the core repository.
Suites have moved to flake.nix and are not anymore in their own folder in the template.
Also, there is two different suites
One for the nixos configurations and one for home manager, what is this about and it that why in the community branch suites are seperated in system and user?
Also, it would be nice in #111 to state that in the review process, if a feature is new, changed place or in any way or form went out of sync with the documentation, the docs have to be changed in the pull request.
This would elevate that kind of problems for the project.
The text was updated successfully, but these errors were encountered: