Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#19859 - plan9port: out of date + excludes important files

Attached to Project: Community Packages
Opened by Fazlul Shahriar (fhs) - Saturday, 19 June 2010, 05:26 GMT
Last edited by Chris Brannon (cmb) - Wednesday, 23 June 2010, 00:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Chris Brannon (cmb)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


The attached PKGBUILD addresses two problems:

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

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:

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.
This task depends upon

Closed by  Chris Brannon (cmb)
Wednesday, 23 June 2010, 00:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  plan9port has been updated.
Comment by Chris Brannon (cmb) - Saturday, 19 June 2010, 13:50 GMT
Both of these ideas seem good.
Will the maintainer remove plan9port-20100520.tgz when he publishes
a new snapshot?
Comment by Fazlul Shahriar (fhs) - Saturday, 19 June 2010, 17:53 GMT
I believe the snapshots are not removed. I still see plan9port-20051127.tgz exists in the server.
Comment by Chris Brannon (cmb) - Sunday, 20 June 2010, 01:23 GMT
Is there any good reason to keep install.log in the new package?
I suppose that info such as the compiler version could be useful to
Comment by Fazlul Shahriar (fhs) - Sunday, 20 June 2010, 01:55 GMT
Nope, there is no good reason to keep it. On the other hand, there's no real reason to remove it either, except for a slightly cleaner package. You can remove install.log. If you do so, I suggest you also remove the other two generated files: install.sum, and config.