FreeBSD ports links
more or less alphabetically. This should all move to the wiki.
- changelog for ports
from Herve Quiroz
Committer's Guide (ports-specific section)
Contributing to the FreeBSD Ports Collection
CPAN port-maker script from tobez
graph tool from Garrett Wollman;
workstation example #1;
workstation example #2 (warning: these are immense!).
extended Makefile targets proposal from (I forget?)
is a package tool wrapper for FreeBSD.
- FreeBSD developer's wiki
- FreeBSD release schedule
- FreeBSD todo list
by Dan Langille; more information than you ever wanted to know about
any and every port;
ports with no subscribers.
linimon's page on the
FreeBSD developer's wiki.
libpkg proposal from Andrew Turner
maintainers with broken ports from Soeren Straarup.
MAKE_ARGS manipulation scripts from Brandon S. Allbery.
- Marcuscom Tinderbox:
a set of software that you can install to create your own test build
environments for ports. Very powerful.
Package building errors by maintainer from Bill Fenner
Package building errors by maintainer from Dirk Meyer
(more of Dirk's links)
- Package building errors (and also complete logs) on the FreeBSD ports
Consider this a "start here" page to learn about why ports do not build.
- Package building procedures
Package building status on the FreeBSD ports build cluster
Shows you how many package builds succeeded, the number that failed, and
scripts from Dirk Meyer.
- Package building status analysis from
*-status.out are the state that each buildenv considers its
ports to be in (e.g. BROKEN/IGNORE/NO_PACKAGE). In general,
these packages are not attempted on the cluster. (To
save time and confusion, only arch-6 and
i386-osrelease are made.)
*-vs-*.diff.out are cross-diffs between each of the above.
This is so that you can find out, e.g., "what ports are marked
BROKEN on i386-7 but not i386-6" or "what ports are marked IGNORE
on amd64 but not i386".
get_why_not_made_* attempts to analyze the reason that
packages that were attempted, failed. These are ports
which are not (yet) marked BROKEN or IGNORE.
is an ncurses front-end to manage the ports collection.
Port Request Form from
- Port Tags Proposal. Finally,
a possible solution to the search-and-browse problem.
port is a simple framework to set ports options in a universal way.
- Porter's Handbook
(which has the list of FreeBSD versions).
Also see the
changes I'd like to make.
port is a small shell script which lets FreeBSD users quickly browse
port descriptions given the port's name or a glob.
port allows you to manage your ports without external databases or
languages (unlike portupgrade). Is is not as feature-full as portupgrade
but may well be more robust.
- Ports ages
by Pav. Hard to read.
- Ports index
- Ports mailing list
- Ports Management Team (portmgr)
policy for supporting 4.X as it reaches end-of-life (EOL);
Quality Assurance (QA) activities.
- Ports Monitoring System (portsmon):
status of one port;
status of all ports for one maintainer;
most recent PRs;
PRs possibly needing assignment;
dependency tree for one port;
patch results for framework PRs.
- ports status for Java ports (from Herve Quiroz);
for Perl ports (from Mathieu Arnold).
(Bill Fenner's survey of ports with unfetchable distfiles)
(by port with problems;
(by www problem)
(fetch list errors)
(status of current run)
Ports section on the "project ideas" page
Ports with possibly newer distfiles (Edwin Groothuis's survey)
report for ports@FreeBSD.org
port allows searching for ports that install some file.
PortsFailingOnPointyhat is a list of some "problematic" ports that
seem to only fail on pointyhat (e.g. not on tinderboxes or real
systems). This is here partially as a reminder to portmgr members not
to repeatedly bother the port maintainers and committers even though
they keep failing on the cluster. These are all things that need to
be investigated (possible bugs in the cluster scripts?)
port is the most widely-used port to allow you to manage your ports. There
is an ideas page for
future capabilities and bugfixes.
Problem Report (PR) handling guidelines
- PR statistics in graphical form (from Brian S. Dean);
in tabular form,
(from Pav Lucistnik);
arrival rate graph
port is a utility for searching the FreeBSD Ports Collection.
It allows you to use regular expressions, and has support for searching
the long description (pkg-descr files)
- Query PRs:
PRs for Linimon;
PRs from Linimon;
PRs involving Linimon.
Release Engineering for Third Party Packages
Rewrite Of Options wiki page. OPTIONS have always managed to be
controversial; if you agree, and want to see them fixed, please help
contribute to this project.
A script for
generating OpenOffice dependencies using GraphViz
A script to find
unmaintained ports with possible new versions, build errors, and related
PRs, from Dryice Liu.
security branch for ports (experimental):
An experimental project run by Jun Kuriyama to create a branch for
the Ports Collection which would only get security updates. This is
basically a test to see how much support there would be for this
concept, which, if it were truly huge, could lead us to re-evaluate
the way we do ports releases.
Security Team Support Matrix. This contains the release date,
release type, and estimated EOL of secteam support, for every
scripts for maintaining a local ports hierarchy:
from Novell forge (expanded version).
various committer activity tables
(note: the "idle commit bits" pages are stale.)
www build status
other port systems links
more or less alphabetically. (Note: refreshed 20110308).
miscellaneous ports links
more or less alphabetically.
At one time I was working on some code that performed a similar function
to Edwin's survey. At the current time, it is still a
total hack, but if you're interested, see
games/xgalaga (original mastersite disappeared)
Here is the backup
net/hinfo for which
the master site,
is generally unreachable from the FreeBSD build machines. Complain
to the original author if you like; but note, he is the most aggressive
person in terms of blocking mail I've ever encountered, and once you're
on his block list (even if it's because you're in a /24 that once had one
spammer in it!), there is no reasonable way to get off of it.
(I, of course, cannot complain to him about this directly. Every
email account I've ever had cannot reach the man. Nevertheless,
the utility itself is useful, even if he's a crank.)
Wed Mar 9 05:50:46 UTC 2011