search

nix-community / lorri

Your project’s nix-env [maintainer=@Profpatsch,@nyarly]
Apache License 2.0
677 stars 24 forks source link

current maintenance status of project #85

Open NANASHI0X74 opened 2 years ago

NANASHI0X74 commented 2 years ago

Describe the bug This project makes somewhat of a messy/neglected impression- the latest github release seems the same as the one in nixpkgs, but is apparently outdated (nixpkgs still points to the old target/lorri repo) and to get the latest version, one needs to use the lorri self-upgrade command, after which the version information printed by lorri -V will remain unchanged. Documentation also seems outdated in some parts- the help text for lorri self-upgrade reads:

rolling-release    Upgrade to the current rolling-release version, will be fetched from git and built locally.
                       rolling-release is expected to be more stable than canon. (default)

But using that default seems to "upgrade" to an older version than the one in nixpkgs. (Doesn't the idea of having a self-upgrade command go against the idea of nix anyway, since this is mutable state outside of the nix config?) There are several stale PRs e.g. #63 https://github.com/nix-community/lorri/blob/canon/MAINTAINERS.md seems outdated (release.nix numbers don't seem to follow semantic versioning)

Expected behavior lorri version in nix should be the current version should lorri self-upgrade be removed? documentation/help text/default upgrade channel should be updated or at least outdated documentation removed Is this repository currently maintained? Who is/are the current maintainer(s)?

nyarly commented 2 years ago

Thanks for your patience here!

I've just joined maintenance on lorri; I'm looking at a number of these issues and trying to review PRs as I go. @Profpatsch has started a monthly "office hours" we'll both be attending to talk about PRs and design decisions over time; the calendar for that is in IRC.

With regards to self-upgrade, I'd suggest that belongs in a separate issue for discussion.

Profpatsch commented 2 years ago

@NANASHI0X74 The basic state of the project is that it works, some (many?) people use it as their daily driver, it has a few quirks, but not a lot of person-power is available for adding features/squashing the remaining bugs & improving the tool.

nyarly commented 2 months ago

We've now shipped 1.7.0 with Flakes support. There are some ideas for features still in progress, but it does work as a daily driver for Nix development.