Skip to content

Conversation

@Computerdores
Copy link

The following points apply when adding a new repository to repos.json

  • I ran ./bin/nur format-manifest after updating repos.json (We will use the same script in github actions to make sure we keep the format consistent)
  • By including this repository in NUR, I confirm that any copyrightable content in the repository (other than built derivations or patches, if applicable) is licensed under the MIT license
  • I confirm that meta.license and meta.sourceProvenance have been set correctly for any derivations for unfree or not built from source packages

Additionally, the following points are recommended:

  • All applicable meta fields have been filled out. See https://nixos.org/manual/nixpkgs/stable/#sec-standard-meta-attributes for more information. The following fields are particularly helpful and can always be filled out:
    • meta.description, so consumers can confirm that that your package is what they're looking for
    • meta.license, even for free packages
    • meta.homepage, for tracking and deduplication
    • meta.mainProgram, so that nix run works correctly

@Computerdores
Copy link
Author

I have one question regard the 2nd todo point: The one package currently in my repo is licensed under AGPLv3, and the derivation is fetched during the build process. All of the code that is in my nurpkgs repo is itself MIT licensed though. Is that fine?

@Computerdores
Copy link
Author

Computerdores commented Nov 20, 2025

Also, I am acutely confused why the evaluation fails. running nix build .#portal-escape in my nurpkgs repo works fine but here it seemingly fails. I suspect it has something to do with this line. However, I think that that should still count as a fixed-output derivation (see nixpkgs doc), which would be the only reason I can see for why it would fail.

I was wondering whether someone else maybe has an idea there, as I am still in the process of figuring out how stuff works with nix packaging and such.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant