raito/lanzaboote
0
0
Fork 0
Code Issues 45 Pull requests 6 Projects Releases 6 Packages Wiki Activity Actions

Npins support #465

Closed
Rexcrazy804 wants to merge 3 commits from npins-support into master
pull from: npins-support
merge into: raito:master
Conversation 9 Commits 3 Files changed 2 +134
Rexcrazy804 commented 2025-07-04 21:17:25 +00:00 (Migrated from github.com)
Copy link

Enables overriding inputs on non flake systems.

Enables overriding inputs on non flake systems.
👍 1
blitz (Migrated from github.com) reviewed 2025-07-04 21:17:25 +00:00
Rexcrazy804 commented 2025-07-04 21:20:00 +00:00 (Migrated from github.com)
Copy link

might have to relocate buildRustApp.nix and document how this can be used.

might have to relocate buildRustApp.nix and document how this can be used.
Rexcrazy804 commented 2025-07-05 10:23:35 +00:00 (Migrated from github.com)
Copy link

for anyone interested in seeing how its used in a npins based nixos configuration at its present state, you may refer this pr

for anyone interested in seeing how its used in a npins based nixos configuration at its present state, you may refer [this pr](https://github.com/Rexcrazy804/Zaphkiel/pull/52)
blitz (Migrated from github.com) requested changes 2025-07-16 13:47:36 +00:00
blitz (Migrated from github.com) left a comment
Copy link

Hi @Rexcrazy804, thanks for the contribution. Unfortunately, we can't accept it in this state, because it duplicates dependency management and we as maintainers would have to bump dependencies in two places.

So while I'm sympathetic to your usecase, my requirement would be to:

  1. Not track dependencies in two places.
  2. Still be able to use a bot for dependency bumping.

Also, I think some version of flake-compat can already do what you want: https://github.com/nilla-nix/flake-compat?tab=readme-ov-file#usage

Let me document this.

Hi @Rexcrazy804, thanks for the contribution. Unfortunately, we can't accept it in this state, because it duplicates dependency management and we as maintainers would have to bump dependencies in two places. So while I'm sympathetic to your usecase, my requirement would be to: 1. Not track dependencies in two places. 2. Still be able to use a bot for dependency bumping. Also, I think some version of flake-compat can already do what you want: https://github.com/nilla-nix/flake-compat?tab=readme-ov-file#usage Let me document this.
Rexcrazy804 commented 2025-07-16 19:27:01 +00:00 (Migrated from github.com)
Copy link

I suppose we could remove the npins folder and mandate sources to be passed externally, this is typically what will be done on the user's end and they'll probably npins import-flake the flake.lock of this repo or add em manually. I'll document the required sources. This should resolve the points you've raised

I suppose we could remove the npins folder and mandate sources to be passed externally, this is typically what will be done on the user's end and they'll probably `npins import-flake` the `flake.lock` of this repo or add em manually. I'll document the required sources. This should resolve the points you've raised
Rexcrazy804 commented 2025-07-16 19:38:20 +00:00 (Migrated from github.com)
Copy link

I've tried working with that fork of flake-compat a while ago but was unable to succeed with the overrides. I'll attempt to try that again and hopefully assist you with documenting it if that is preferred.

I've tried working with that fork of flake-compat a while ago but was unable to succeed with the overrides. I'll attempt to try that again and hopefully assist you with documenting it if that is preferred.
blitz commented 2025-07-24 13:45:27 +00:00 (Migrated from github.com)
Copy link

Does #469 work for you?

Does #469 work for you?
Rexcrazy804 commented 2025-07-24 19:25:42 +00:00 (Migrated from github.com)
Copy link

A bit occupied to test it out now but, the expressions there does look good to me

A bit occupied to test it out now but, the expressions there does look good to me
👍 1
Rexcrazy804 commented 2025-07-24 19:26:33 +00:00 (Migrated from github.com)
Copy link

closing this pr

closing this pr

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
blitz
Labels
Clear labels   
bug

Something isn't working

  
dependency

Issues related to our dependencies

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
review-next

   
security

   
stub

   
tool

   
wontfix

This will not be worked on

No labels
bug
dependency
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
review-next
security
stub
tool
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: raito/lanzaboote#465
No description provided.
Delete branch "npins-support"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?