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
pythonPackages.rotate-backups: init at 6.0 #64989
Conversation
@GrahamcOfBorg build python3Packages.rotate-backups Since this is an application AFAIU, I'd suggest adding an alias at the top level. |
@lheckemann I will look into it! Some of the dependencies like coloredlogs is also a application.. Will check which are and which aren't :) |
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.
A lot of them nit picks.
Sorry for the spam :)
for converting a python libray to an application, just create the library as a python-module, then in all-packages.nix you can do something to the effect of:
|
@jonringer should incoperate everything you asked, and also @lheckemann should have added all which are applications. :) |
for adhering to the CONTRIBUTING.md, I think people expect that 1 commit relates to all changes for a given package. Although the little "auto commit changes" feature is nice in github, it does make the commit history polluted with a bunch of small commits. I think it's prefered to do all the changes i suggested to their related commit, or at the very least, squash all the tiny commits into one that makes sense. I'm sure someone else will have a stronger opinion on the matter. |
Not taking that into account, will be squashed later. Didn't want to do it
now if there was any mistakes
…On Thu, 18 Jul 2019, 19.24 Jon, ***@***.***> wrote:
for adhering to the CONTRIBUTING.md
<https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md>, I
think people expect that 1 commit relates to all changes for a given
package. Although the little "auto commit changes" feature is nice in
github, it does make the commit history polluted with a bunch of small
commits.
I think it's prefered to do all the changes i suggested to their related
commit, or at the very least, squash all the tiny commits into one that
makes . I'm sure someone else will have a stronger opinion on the matter.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#64989?email_source=notifications&email_token=AGGAWSVV3KJTOEH6QHPC3QLQACRNPA5CNFSM4IERWH52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2JGILY#issuecomment-512910383>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGGAWSXU6FLF7Y42PUDEF33QACRNPANCNFSM4IERWH5Q>
.
|
|
I've opened a PR upstream (xolox/python-coloredlogs#74), so
After that |
Should be good to go now :) |
@GrahamcOfBorg build pythonPackages.rotate-backups |
Why are the python-modules being called in |
@worldofpeace the packages that is aliased in EDIT: Note that it is not all modules that are in |
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.
Comments apply to multiple things.
@worldofpeace should be fixed now! |
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.
some minor nitpicks, otherwise LGTM
nix-review
passes on NixOS
Fixed, should be good to go now :) |
Motivation for this change
Wanting roate-backups, but keep in mind it has A LOT of dependencies which depend on each other.
I have done my best to keep it clean, and make as many tests as possible work.
I couldn't find a good way to put them into the python-packages.nix file, as the alphabetic order is.. Non existing. So I have grouped them together.
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)