summary refs log tree commit diff
path: root/elpa.org
diff options
context:
space:
mode:
authorCrazazy2022-02-22 15:58:13 +0100
committerCrazazy2022-02-22 16:12:05 +0100
commit42c1efb63b8f9ae5a107217538d5c247abd0ebe6 (patch)
treed0acf8313024e78159eb149c6b3ec8a6c42f79c0 /elpa.org
parentaa990b166b50829ecedf2b8090e46c4b617d8bcc (diff)
add elpa info org file
Diffstat (limited to 'elpa.org')
-rw-r--r--elpa.org36
1 files changed, 36 insertions, 0 deletions
diff --git a/elpa.org b/elpa.org
new file mode 100644
index 0000000..cae3bb1
--- /dev/null
+++ b/elpa.org
@@ -0,0 +1,36 @@
+#+Title:Tilde elisp package archive
+#+Author: Crazazy
+#+INCLUDE: ./style.org
+
+I decided that I didn't want to interact with other people when
+publishing my package, because somehow I'm antisocial like that
+This means that there is now a new package repository available for
+you to use
+* Installation
+  Usage of the repo is similar to how you'd install melpa and stuff
+  #+begin_src elisp
+    (add-to-list 'package-archives '("tilde" . "https://tilde.cafe/~crazazy/elpa/"))
+    (package-refresh-contents)
+  #+end_src
+* Adding your own package
+  Right now this archive is kinda barren, and the amount of packages
+  is countable on 1 hand. You can help change that! Just send a mail
+  to [[mailto:crazazy@tilde.cafe][crazazy@tilde.cafe]] with your package where it is located and if
+  you have any special files that need to be put in there (or just
+  send a whole [[https://github.com/melpa/melpa#recipe-format][MELPA recipe]], I use those internally anyways)
+** What I'm looking for
+   There are /some/ standards that I want to follow in order to give
+   this package repository a more tilde-like or grassroots-style
+   feel. Mostly this means:
+   - Don't host your package on github.com or gitlab.com
+   - Don't depend on melpa (prefer if you depend just on packages from
+     [[https://gnu.elpa.org][GNU elpa]] but nonGNU is fine). The reason for this is that melpa
+     is *HUGE*. You can seriously improve update time if you don't
+     refresh melpa automatically, and it is not installed by default
+     on an emacs system.
+** This all sounds awfully strict
+   While I would like the non-github requirement, if you really,
+   /really/ have to use melpa, there is a quelpa package in this
+   repository for you as a safeguard. I just strongly advise against
+   using it since quelpa /does/ pull down the entire melpa recipe
+   archive, which, again, is big.