lib: export namespaced lib as normal overlay #145
Closed
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.
Draft: this still is a public thought journey
Offspring: #147 , blaggacao#3
todo: a flollowup commit could change caller sites within this repo to
use
pkgs.devos.lib
/nixos.devos.lib
, as well.(Hypothetical) lib-only usage
and then:
Namespaceing with litteral
devos
implies sticky ownership of those parts bydivnix/devos
.I reason that this might be the right way of thinking about the
./lib
folder, though:devos.lib
)./lib
since that makes syncing with the mothership ever more difficult. I've started by placing repo-specific library functions under./pkgs
On the other hand, we might also conclude that it is better to namespace with the current project's name, regardless if those are upstreamable changes and encourage to put all repo-specific library functions under
./lib
.Thinking out loud, I'm actually not sure any more. Maybe upgrading
./lib
is the better road of the two.