Add ekapkgs rebase plan as alternative to nixpkgs fork strategy - #10918
Open
jonringer wants to merge 1 commit into
Open
Add ekapkgs rebase plan as alternative to nixpkgs fork strategy#10918jonringer wants to merge 1 commit into
jonringer wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ekapkgs was designed to be a poly repo package set, so having Omarchy as a "downstream package repository" is a first class supported use case.
Some of the language around
eka-ci,ekapkgs-cli, and other tooling should have a grain of salt as some of the features mentioned are planned but not yet implemented.This plan is generated more from as "address all items in the nix.md" plan, rather than a holistic version of what I had in mind for "knocking your socks off" leveraging Nix as a base for "solving software issues with Nix, rather than trying to get software to adhere to Nix's high bar of purity." For example, I also had some ideas around enabling a lot of FHS workflows fthrough
nix-ldand potentially extending it's feature set, so that downloaded binaries with non-crazy library dependencies still worked.Go to the "Improvements from original nix plan" section if you want the cliffnotes version of what I'm proposing.
Throwing this up here as a thought experiment.