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
_3llo: init at 0.3.0 #65370
_3llo: init at 0.3.0 #65370
Conversation
Why is there an underscore in the attribute name when the repo doesn't name the tool that way? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expression looks fine to me.
Not sure about its place in nixpkgs though.
It would be nice if this program self documented itself instead of erroring ungracefully when you don't set the aforementioned environment variables
|
Nix doesn't like attribute names with a number at first. I was unsure how to deal with this and I just used this pattern from other tools like
In fact you're right. Not sure if I can make it today, but I'll prepare an upstream patch for this (unless there's something that just didn't land in the release :) )
Hmm, probably yes.... I'd like to note though that I actually dislike this section-based approach as it makes it IMHO way harder to find an appropriate place for a new package and I honestly doubt that many people benefit from this... at least whenever I look for something I either grep over |
I think we can just make it
That would be really excellent if you did ✨
I think it helps with breaking up the psuedo alphabetization. Then at least you can see it restarting |
But isn't that counter-intuitive when you want to add a bunch of packages like |
Huh, we would then get a syntax error when referencing it in the function arguments of a package
I don't think there's a guideline in the Nixpkgs manual about this, rather unfortunate that it would have to be |
@worldofpeace updated. Would be awesome if you could review the upstream patch as well. Please keep in mind that I had to change a minor detail in |
Gave it a review @Ma27 |
Simple CLI client for `trello.com`. It can be used like this: ``` $ export TRELLO_USER=your_username $ export TRELLO_KEY=your_key $ export TRELLO_TOKEN=your_token $ ./result/bin/3llo ``` I didn't create a module for this as I don't think that those secrets should live in the Nix store. Ideally `3llo` can be used from a script which retrieves secrets from some kind of password store like this: ``` export TRELLO_KEY=$(pass show trello/key) export TRELLO_TOKEN=$(pass show trello/token) 3llo $@ ```
The `gemset` field can be an attribute set as well in `buildRubyGem`, however attribute sets can't be coerced to strings for the environment set. The impact should be relatively small as the environment variables are only used by the `runCommand` script for `bunlderApp` which doesn't refer to `gemset` at all.
@worldofpeace updated the patch :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @Ma27.
Motivation for this change
Simple CLI client for
trello.com
. It can be used like this:I didn't create a module for this as I don't think that those secrets
should live in the Nix store. Ideally
3llo
can be used from a scriptwhich retrieves secrets from some kind of password store like this:
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)