summaryrefslogtreecommitdiff
path: root/README.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to 'README.asciidoc')
-rw-r--r--README.asciidoc7
1 files changed, 6 insertions, 1 deletions
diff --git a/README.asciidoc b/README.asciidoc
index 607f02e..921e96e 100644
--- a/README.asciidoc
+++ b/README.asciidoc
@@ -9,6 +9,7 @@
/nɪks.təˈmal/ ("nix-tamal")
Maker:: toastal
+Website:: https://nixtamal.tech (launching soon)
Put out:: 2026
@@ -30,7 +31,7 @@ Nixtamal is a tool to pin input version like its predecessors niv, npins, Pinch,
* keeps a stable reference pin to supported VCSs
* supports mirrors for fetching [1]
-* supports patch-based VCSs, like Pijul & Darcs, in a first-class sense (tho nixpkgs will be required due to Nix builtins fetchers limitations)
+* supports patch-based VCSs, like Pijul, Darcs, & Fossil, in a first-class sense (tho nixpkgs will be required due to Nix builtins fetchers limitations)
* uses a KDL manifest file with templating instead of CLI input
* supports arbitrary commands for getting the latest change for inputs
* refreshes inputs; skips frozen
@@ -40,6 +41,7 @@ Nixtamal is a tool to pin input version like its predecessors niv, npins, Pinch,
* source code & community will never be hosted on a proprietary, privacy-invasive, megacorporate platform with obligations to shareholders or venture capital
* licensed for your freedom
* ML-family programming (feels closer to Nix)
+* supports schema versioning for manifests and lockfiles
Future goals (planned but not yet implemented):
@@ -136,6 +138,7 @@ Opens text editor. & After editing …
----
$ nixtamal lock
$ nixtamal refresh
+$ nixtamal upgrade
----
=== What next?
@@ -305,6 +308,8 @@ For details read LICENSE.txt with full license texts at license/.
Currently this is best done by sending a patchset to toastal+nixtamal@posteo.net or DM me a remote to clone @ toastal@toastal.in.th.
+Website: https://nixtamal.tech
+
Community is in an XMPP MUC (chatroom) with future hopes to have an IRC gateway. Join @ xmpp:nixtamal@chat.toastal.in.th?join.
Additionally, please read the PITCHING_IN.rst file for other information/expectations.