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
cut-the-crap: init at 1.0.0 #75794
cut-the-crap: init at 1.0.0 #75794
Conversation
@jappeace Would you consider releasing this to Hackage? That way, it would get updates automatically here in nixpkgs whenever you released a new version. |
Hi @cdepillabout I uploaded it to hackage. |
@jappeace Thanks! Next time the hackage packages are updated on the
You should be able to add that with a wrapper script. Here's an example: nixpkgs/pkgs/development/haskell-modules/configuration-nix.nix Lines 585 to 593 in a8144b1
For cut-the-crap, it might look something like this: cut-the-crap =
let path = stdenv.lib.makeBinPath [ ffmpeg ];
in overrideCabal (addBuildTool super.cut-the-crap makeWrapper) (_drv: {
postInstall = ''
wrapProgram $out/bin/cut-the-crap \
--prefix PATH : "${path}"
'';
}); |
system-filepath temporary text unliftio-core | ||
]; | ||
prePatch = "hpack"; | ||
license = stdenv.lib.licenses.mit; |
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.
Why is there no meta
as with any regular derivation? Maybe I'm just not familiar with the Haskell ecosystem...
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.
This is generated, but at the moment I'm waiting for haskellPackages to be updated so I can just do cdepillabout's suggestion.
src = fetchgit { | ||
url = "https://github.com/jappeace/cut-the-crap"; | ||
sha256 = "1z4s0zan421q4722k32p0n33bsh7di1m6pbbdzqi7j87lfd9i7nk"; | ||
rev = "0ea8a0a0fd3e8d85f44337f13ef2445d22d1bf97"; |
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.
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.
I made this before that debian thing. I wouldn't know how to use tags, or do you just mean the same commit as that tag?
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.
Maybe that's also automatically generated... I'll leave this review to someone else more familiar with Haskell :)
@cdepillabout didn't you mean stackage, not hackage? |
@turion What are you referring to?
However, it appears that @jappeace has since uploaded to Hackage, so now it should be easy to just use Although you're right that uploading to Stackage (in addition to Hackage) would make it easier to make sure |
@cdepillabout Thanks for the clarification! I can never remember how, in which files, and in which workflow either hackage or stackage are crawled. (Wish this was documented.) |
@turion Yeah, I definitely sympathize! A (very short) explanation is that Haskell packages are updated from Hackage automatically on a daily basis in this file: The packages in the stackage resolver are specified here:
This list is updated once a week or so by peti. I believe he does it semi-automatically. That file also has a bunch of other settings for special things to do when updating packages from Hackage. |
I'll fix this up right now as discussed above (eg use haskellPackages) |
Ok nice, that's a lot less code and it makes updating this as simple as re-uploading to hackage. Thanks for all the help @cdepillabout |
@jappeace One more thing. Could you rebase this on the We like to have most Haskell-related changes going to the |
This reverts commit fe6addb.
This is really essential thing that everyone should be doing. A few extra notifications won't hurt anyone, and we should be tracking issues to connect them to the best people who can handle them. Co-Authored-By: Cole Helbling <cole.e.helbling@outlook.com>
lol, that upsets github quite a bit @cdepillabout |
I kindly refer you to #85438 Sorry for everyone else who got tagged. I didn't expect github to be so un-intelligent. |
@jappeace please mind your language 🙏 . It's 1 thing we add here a program that has "crap" in it's name - it doesn't mean we have to use such words when we deal with them. |
@doronbehar I already self censored. You probably had a tab open or something. |
I noticed that and I still felt it was necessary to put it. I was subscribed to this issue and I got that by email. |
Motivation for this change
Adds a useful automated video editing tool for streamers.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
I think I'm the maintainer of this package
cc @