project

Others probably have not fully realized this yet, but with GitHub one can: 1) Publish arbitrary commits under your https://github.com/my/project URL, e.g. a fake https://github.com/my/project/blob/<faked_commit>/README.md in your project describing how to install it that actually describes installing malware. 2) Publish those commits under your name, with your email address, and GitHub will prominently display it as if you made the commit (most do not use GPG signatures, and most do not know to look for "Verified" anyway) It seemed only a matter of time before this behavior got abused for something (anti-DMCA action is perhaps the best outcome of this situation I can imagine..)

The "learn+fuzz" part seems to always produce weird results due to my navigational habits, so I have a zero-dependency very short {ba,z}sh function that allows me to jump to preset locations (kd for "quicK Dir" or "worK Dir"): $ cd ~/go/src/github.com/my/project $ kd awesome_project $PWD # create bookmark Then, anywhere: $ kd aw # BAM $ # yay, straight to my project! Also, if I'm in a project with a "root", like a Makefile, Gemfile, or anything: $ cd app/controllers/whatever/deeply/nested $ kd # back to the project root! $ make I'll probably integrate it with fzf some day but for now the "prefix thing+match last entry" works well enough. https://gitlab.com/lloeki/dotfiles/blob/master/shell/kd

> nix-pkg -i github.com/my/project What you describe would be fairly easy to script. I'm playing around with similar ideas. It's not exposed by default, but the included script `nix-prefetch-git` dumps a git repo into the nix store, and when you run it from your shell, you have access to ssh keys and ssl certs (that are unavailable within a normal nix build). The next step is harder like you say, you'd either need to include nix expressions for all dependencies on down through libc and gcc, or just assume/hope that "whatever happens to be in the local nixpkgs" is appropriate, but then you kinda lose out on a lot of the point of nix. It'd be nice if there were some way to reference a version of nixpkgs from which the expressions for "ruby20" and its dependencies would be drawn (but then you'd end up with hundreds of slightly different ver

It would be nice if there was a github/remote integration. `nix-pkg -i github.com/my/project` would clone the repo and install the dependencies found in the deps.nix file in the root of the repo. Right now, versions are just loosely selected so it would be (eg: there's a ruby193 and ruby20). If one version gets dropped in nigpkgs or the selector is not specific enough breakage would easily happen.