nvh started out as a fork of n. As nvh evolved, the differences between the two code bases became significant. To make it easier to continue submitting clean Pull Requests upstream to n, I made a hard fork so that I could work on them separately.
I am now the maintainer for n and have ported most of the improvements there too. I am now making changes in n first, and nvh is falling behind! Rather than continue to maintain two similar-but-different code bases, I plan to archive nvh.
An interesting difference between n and nvh is using cp and rsync for installs. n is broken on archlinux by symlinks below the top level.
If this or any other differences are important to you, please open an issue here (until archived) or open an issue on n.
nvh
started out as a fork ofn
. Asnvh
evolved, the differences between the two code bases became significant. To make it easier to continue submitting clean Pull Requests upstream ton
, I made a hard fork so that I could work on them separately.I am now the maintainer for
n
and have ported most of the improvements there too. I am now making changes inn
first, andnvh
is falling behind! Rather than continue to maintain two similar-but-different code bases, I plan to archivenvh
.An interesting difference between
n
andnvh
is usingcp
andrsync
for installs.n
is broken on archlinux by symlinks below the top level.If this or any other differences are important to you, please open an issue here (until archived) or open an issue on
n
.