In the `external' case, the copy of the code is not kept here but in the
`externals/<pkg>' branch in the `elpa' repository.
+
You can check out all the external packages into the `packages' directory
with the command:
make externals
+You can check out a specific external PACKAGE into the `packages'
+directory with these commands:
+
+ cd packages
+ git clone --reference .. --single-branch --branch externals/PACKAGE $(git config remote.origin.url) PACKAGE
+
+If you already have a packages/PACKAGE directory with a previous
+checkout, you can update it like this:
+
+ cd packages/PACKAGE
+ git pull
+
** Public incubation
If you want to develop a package publicly prior to its first release (to
benefit from others' feedback, primarily), but not in an external repo,
-you can push to an "ephemeral" branch -- subject to rebase and eventual
-removal upon finishing merge -- for the duration of the incubation.
+you have 2 choices:
+- you can simply put "Version: 0" to indicate that this should not be
+ released yet.
+- or you can push to an "ephemeral" branch -- subject to rebase and eventual
+ removal upon finishing merge -- for the duration of the incubation.
* DEPLOYMENT
git clone .../elpa
mkdir build
cd build
+ (cd ../elpa; git log --format=%H | tail -n 1) >.changelog-witness
ln -s ../elpa/admin
ln -s ../elpa/GNUmakefile
admin/update-archive.sh