print a deprecation warning for the cursed channel:
"file" syntax #345
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#345
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
File arguments like in
nix-build
andnix build -f
, when prefixed bychannel:
, redirect to a hardcoded URL pattern of the formhttps://nixos.org/channels/FOO/nixexprs.tar.xz
. We should deprecate and lint on this because oh my godsBrought up in https://gerrit.lix.systems/c/lix/+/1186/comment/b725fef2_4076655f/
cc @jade
I actually use this personally; mostly in the form of
NIX_PATH=nixpkgs=channel:nixos-unstable nix-shell -p foo
for fetching something fromnixos-unstable
quickly. I don't strongly mind it being deprecated but it's useful to point out that people do use it :pYes, and it is in nix.dev. We should nevertheless deprecate it because it's super questionable.
yeah; I'm not too fussed since it's nixpkgs-specific; it might be a good first example for #342 (aka a
nix-shell
but nixpkgs-specific, including easy channel selection) even.That specific use might actually be a rare case where the local flake registry could be useful for creating a shorthand rererence
This is a reasonable use case, but the name
channel:
is very cursed, and perhaps should benixpkgs:
or something like that. I dunno. I understand it is a useful thing to have, but the actual implementation as hardcoding the authority being nixos on it is kind of dubious tbh.this actually sounds like something that should perhaps be generalized instead of removed: maybe add an option to define custom urn schemes as regex replacements, and make
channel
just one of them that's shipped in nixpkgs by default?That would be reasonable