[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[nongnu] master fed355f: * README.org: Prefer org syntax and prepare for
[nongnu] master fed355f: * README.org: Prefer org syntax and prepare for export.
Sat, 28 Nov 2020 07:33:27 -0500 (EST)
Author: Stefan Kangas <email@example.com>
Commit: Stefan Kangas <firstname.lastname@example.org>
* README.org: Prefer org syntax and prepare for export.
README.org | 63 +++++++++++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 48 insertions(+), 15 deletions(-)
diff --git a/README.org b/README.org
index 593e9fa..0a4dc40 100644
@@ -1,54 +1,70 @@
#+TITLE: NonGNU ELPA README
Copyright (C) 2020 Free Software Foundation, Inc.
See the end of the file for license conditions.
This repository contains the sources, deployment scripts, and auxiliary files
-for NonGNU ELPA (elpa.nongnu.org).
+for [[https://nongnu.elpa.org][NonGNU ELPA]] (=elpa.nongnu.org=).
This file explains the repository layout, how to add and edit packages, and how
-to deploy the archive (either on elpa.nongnu.org, or a local copy for testing
+to deploy the archive (either on =elpa.nongnu.org=, or a local copy for testing
* Building the archive
To build the archive(s), all it takes is:
- git clone .../nongnu.git
+ git clone .../nongnu.git $FOO
which you presumably have done already if you're reading this file.
-This will build all the tarballs as well as the `archive-contents` file and
-put them into the `archive` and `archive-devel` subdirectories.
+This will build all the tarballs as well as the =archive-contents= file and
+put them into the =archive= and =archive-devel= subdirectories.
If the archive exists already, it will only build those tarballs that are new.
-You can also (re)build a specific package [PKG] with:
+You can also (re)build a specific package =[PKG]= with:
If you want to force a rebuild of a tarball that was already built, you have
rm archive/[PKG]-[VERSION].tar; make build/[PKG]
* Using packages in-place
The packages can be installed and used in-place. First you need to make
-sure the package(s) you can about are placed in the `packages` subdirectory,
-e.g. with `make externals`, and then you can to add that `.../packages`
-to your `package-directory-list`. And once that is done you can do:
+sure the package(s) you can about are placed in the =packages= subdirectory,
+e.g. with =make externals=, and then you can to add that =.../packages=
+to your =package-directory-list=. And once that is done you can do:
-to create the [PKG]-pkg.el and [PKG]-autoloads.el file as well as compile
+to create the =[PKG]-pkg.el= and =[PKG]-autoloads.el= file as well as compile
all the ELisp files in that package. You can also do that on all the
* Guidance for accepting packages
@@ -164,29 +180,34 @@ packages with:
* Adding a package
-Once it is decided we want to add a [PKG], here's what it takes:
+Once it is decided we want to add a package =[PKG]=, here's what it takes:
- Fetch the upstream code with something like:
+ #+begin_src sh
git fetch [PKGREMOTE]
- Let's say the code is now in [PKGBRANCH].
+ Let's say the code is now in =[PKGBRANCH]=.
-- Push that code to nongnu.git:
+- Push that code to =nongnu.git=:
+ #+begin_src sh
git push nongnu [PKGBRANCH]:refs/heads/externals/[PKG]
-- Add a corresponding entry to the file `externals-list`.
+- Add a corresponding entry to the file =externals-list=.
- Make sure the resulting tarball looks good and works well.
- Commit and push that change:
+ #+begin_src sh
git commit -m 'New package [PKG]'
@@ -204,3 +225,15 @@ GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with NonGNU ELPA. If not, see <http://www.gnu.org/licenses/>.
+#+AUTHOR: NonGNU ELPA Maintainers
+paragraph-separate: "[ ]*$"
+time-stamp-pattern: "4/#\\+DATE: %Y-%02m-%02d$"
|[Prev in Thread]
||[Next in Thread]|
- [nongnu] master fed355f: * README.org: Prefer org syntax and prepare for export.,
Stefan Kangas <=