Skip to content
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

semi automatic update for /pkgs #118

Closed
benneti opened this issue Feb 12, 2021 · 5 comments · Fixed by #135
Closed

semi automatic update for /pkgs #118

benneti opened this issue Feb 12, 2021 · 5 comments · Fixed by #135
Labels
enhancement New feature or request

Comments

@benneti
Copy link
Contributor

benneti commented Feb 12, 2021

Is your feature request related to a problem? Please describe.
I do not want to check manually whether my custom pkgs have updates.

Describe the solution you'd like
Add https://github.com/ryantm/nixpkgs-update to the configuration and maybe a litte subcommand to flk to have a simple interface to it (I plan to try it myself when I have some more time).


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@nrdxp nrdxp mentioned this issue Feb 15, 2021
17 tasks
@nrdxp nrdxp added the enhancement New feature or request label Feb 17, 2021
@benneti
Copy link
Contributor Author

benneti commented Feb 21, 2021

I just tried out nixpkgs-update and I think that I neither fully understand how to use it nor that it does exactly what we would need to.

@nrdxp
Copy link
Collaborator

nrdxp commented Feb 21, 2021

This is a problem flakes could actually solve for us. We could do it right now, I just don't want to flood the inputs with a huge list of package sources, which is why I started that dicussion.

Although I guess, if it's only in the community branch, it wouldn't be horrible, if we have to.

@benneti
Copy link
Contributor Author

benneti commented Feb 22, 2021

thats actually a super cool idea.
A small down side would be that (as far as I understand it) it would only work with git repositories (i.e. not with binary releases).

@nrdxp
Copy link
Collaborator

nrdxp commented Feb 22, 2021

IIRC, flakes now have a mercurial backend, as well as the ability to simply point to an https url with a tarball. So I think binary should be possible, you just have to handle the input differently.

@benneti
Copy link
Contributor Author

benneti commented Feb 22, 2021

this sounds better and better!

nrdxp added a commit that referenced this issue Feb 23, 2021
* Update documentation with an example.
* Add `mkVersion` function to autogenerate a version string.
* Add srcs package via overlay containing all sources defined in
  _pkgs/flake.nix_
* Extend `flk update` with the ability to only update the given input
nrdxp added a commit that referenced this issue Feb 26, 2021
* Resolves #118
* Leverage flakes to manage package sources & hashes
* Update documentation with an example.
* Add `mkVersion` function to autogenerate a version string.
* Add srcs package via overlay containing all sources defined in
  _pkgs/flake.nix_
* Extend `flk update` with the ability to only update the given input
nrdxp added a commit that referenced this issue Feb 26, 2021
* Resolves #118
* Leverage flakes to manage package sources & hashes
* Update documentation with an example.
* Add `mkVersion` function to autogenerate a version string.
* Add srcs package via overlay containing all sources defined in
  _pkgs/flake.nix_
* Extend `flk update` with the ability to only update the given input
Pacman99 pushed a commit that referenced this issue Feb 26, 2022
118: Add patches options to channels r=Pacman99 a=amarshall

This is available in underlying flake-utils-plus.

Co-authored-by: Andrew Marshall <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants