-
-
Notifications
You must be signed in to change notification settings - Fork 200
Sam/custom pam #1772
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
base: develop
Are you sure you want to change the base?
Sam/custom pam #1772
Conversation
5a65e37
to
07162ca
Compare
@samrose What's the advantage of the above compared to callPackage? Overall looks like the flake way is much more verbose. |
@steve-chavez for what it's worth, here are the advantages to using flakes, and the flake-parts framework https://gist.github.com/samrose/a9a19b7fad0aed8fd8355bdf0b87df08 |
01e56d8
to
43363e2
Compare
this and #1765 are directly related. I don't feel like merging the two into one version though, as the change in 1765 is pretty significant already. |
Co-authored-by: Douglas J Hunley <[email protected]>
a796ea8
to
fdd95c8
Compare
@staaldraad I personally support whatever works best for you. I only created this PR to trigger some of the tests and builds and checks that let us know things are working as desired + give a simpler way to see changs. But thought you could either use this PR, or move work as you see fit. |
What kind of change does this PR introduce?
I will follow up with an explanation as to why we use this flake-parts approach soon.
The fundamental reasons are discussed at https://flake.parts/index.html