Expose flake-file.apps as flake apps, not packages

[Adda0]

I was cleaning up my flake outputs and noticed that write-flake, write-lock, write-inputs, and others are exposed as flake outputs packages instead of flake outputs apps.

$ nix flake init --template github:vic/flake-file#dendritic
$ nix flake show
path: <path/to/new/flake>
├───apps
│   └───x86_64-linux
└───packages
    └───x86_64-linux
        ├───write-flake: package
        ├───write-inputs: package
        └───write-lock: package

Since packages are supposed to be build artefacts and/or something installable, and these are, unless I misunderstood the intention, all just quick and small scripts only useful for the current configuration directory and are not expected to be installed and available on PATH for general use in other directories, I think having them as apps would be more appropriate.

Now:

$ nix flake init --template github:vic/flake-file#dendritic
$ nix flake show
path: <path/to/new/flake>
├───apps
│   └───x86_64-linux
│       ├───write-flake: package
│       ├───write-inputs: package
│       └───write-lock: package
└───packages
    └───x86_64-linux

The change is applied only when setting the perSystem flake outputs, so hopefully it should not break anything in flake-ile, as all references use the unmodified flake-file.apps.

Feel free to close the PR if exposing the scripts as packages was intentional or something.

I think the same can be done to https://github.com/vic/den/blob/b7f910ab47260c91a0ae8d55fa72cd2178ba2458/templates/default/modules/nh.nix#L7.

[vic]

Hey @Adda0,

I had no particular reason using packages instead of apps, other than I've never used apps. haha. If I'm understanding correctly, packages is for things that can be consumed downstream (by your flake consumers). Your change makes sense in that regard, feel free to also send a patch for Den