Arch Linux

The attached PKGBUILD addresses two problems:

(1) The current binary package is out of date. This is probably because
the PKGBUILD uses

http://swtch.com//plan9port/plan9port.tgz

and tries to update it through CVS. Plan9port has switched from
CVS to Mercurial and updating it from CVS won't work. We can make
the PKGBUILD work with Mercurial, but this seems to be a very
brittle way of packaging plan9port. The above url is actually
a symbolic link to the latest stable snapshot:

http://swtch.com/plan9port/plan9port-20100520.tgz
(see http://swtch.com/cgi-bin/info.cgi?file=/plan9port/plan9port.tgz).

So, the upstream maintainer can be break the package anytime by
releasing a new snapshot with a different md5sum.

I think the correct way is to package plan9port-$pkgver.tgz. It's
also less confusing to the users, because the version of package
matches the content of the package.

(2) The current PKGBUILD wipes everything in src/, which contains
all the source code for libraries and programs, and also mkfiles that
build them. In my PKGBUILD I leave src/ as-is because

(a) Source code is an important part of plan9port. All
manual pages explicitly references the path to source
code. There's also a src(1) command that opens up the
source to a plan9port command or library function. I
think most people *want* the see the source, especially
if they are developers using plan9port libraries.

(b) More importantly, src/ contains standard mkfiles (with
abstract rules) that are used by 3rd party
programs/libraries. I'm talking about mkhdr, mkone,
mkmany, mkdib, and maybe others. These absolutely should
not be removed.