vicinae: support Home Manager module alongside upstream module

[rwxae]

Description

Adds support for official home-manager options for vicinae (configured via programs.vicinae instead of services.vicinae).

Official options for vicinae in home-manager were added in nix-community/home-manager#8093.

As stated by the author, these options should work the same way:

The code is mostly verbatim from vicinaehq/vicinae@main/nix/vicinae.nix
with the main difference that I moved the logic for packaging extensions into the module itself.

This is not a breaking change, users of the options that come from vicinae flake don't lose anything.

I'm welcome to hear any feedback.

Thank you for this amazing tool!

Closes: #2076

---

• I certify that I have the right to submit this contribution under the MIT license
• Commit messages adhere to Stylix commit conventions
• Theming changes adhere to the Stylix style guide
• Changes have been tested locally
• Changes have been tested in testbeds
• Each commit in this PR is suitable for backport to the current stable branch

[0xda157]

a testbed for the home-manager options should be added

[rwxae]

Applied all suggested improvements, awaiting a review :)

[rwxae]

I've been looking at other examples to better understand how stylix works. And looks like there is no need to check for presence of viciane in programs. It is always going to be true since home-manager provides this option. This check is only needed if the options come from external flake (e.g. zen-browser or vicinae-standalone).

So maybe, a final implementation for eachConfig should be something like this to avoid any confusion:

      eachConfig =
        config:
        let
          finalConfig = {
            vicinae = config;
          };
        in
        {
          services = lib.optionalAttrs (options.services ? vicinae) finalConfig;
          programs = finalConfig;
        };

What do you think?

[0xda157]

this should be merged after nix-community/home-manager#8313 is merged (if it isn't rejected).

[0xda157]

I'd be fine with merging this as, because it seems that nix-community/home-manager#8313 isn't likely to be merged soon.

---

I've been looking at other examples to better understand how stylix works. And looks like there is no need to check for presence of viciane in programs. It is always going to be true since home-manager provides this option. This check is only needed if the options come from external flake (e.g. zen-browser or vicinae-standalone).

So maybe, a final implementation for eachConfig should be something like this to avoid any confusion:

      eachConfig =
        config:
        let
          finalConfig = {
            vicinae = config;
          };
        in
        {
          services = lib.optionalAttrs (options.services ? vicinae) finalConfig;
          programs = finalConfig;
        };

What do you think?

that would break compatibility with older home-manager version, but that is fine as stylix only supports the most recent hm commit (on unstable).

[trueNAHO]

I'd be fine with merging this as, because it seems that nix-community/home-manager#8313 isn't likely to be merged soon.

Yes, this PR LGTM.

@rwxae, could you resolve the merge conflicts?

[rwxae]

@trueNAHO, fine, I'll do it!

[rwxae]

I am so bad at git

Implied approval by the following statement:

I'd be fine with merging this as, because it seems that nix-community/home-manager#8313 isn't likely to be merged soon.

[stylix-automation]

Backport failed for release-25.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-25.11
git worktree add -d .worktree/backport-2068-to-release-25.11 origin/release-25.11
cd .worktree/backport-2068-to-release-25.11
git switch --create backport-2068-to-release-25.11
git cherry-pick -x a4406d9799d002c41296c72378a1094a8fc9aa1b