Version 14 (modified by raimue (Rainer Müller), 12 years ago) (diff)


New Help System for port(1)


The current help system in port(1) is very weak. The man pages are written in old roff format which is difficult to maintain and got neglected for a long time. Therefore this document proposes to develop a new help system for port(1) which will make it both easier for users to access the help and for developers to write and maintain documentation.


The new help system will make use of asciidoc which is already used in other Open Source projects such as git and mercurial. Existing man pages of these projects can serve as reference for ours. Using asciidoc allows to generate multiple output formats out of one single source; especially interesting for us are man pages and DocBook XML. The resulting man page can be included in the base distribution, while the DocBook XML could help to integrate the man pages into the guide.

Asciidoc is already available in MacPorts and therefore easily accessible to all developers.

Help invocation from port(1)

As previous calls for participation to enhance port help went unheard, here is a proposal for a totally different system inspired by git. The documentation will be available as man pages, therefore port help <topic> will become an alias of man port-<topic>. This means it can be easily accessed from the command line. Once the man pages are also available online, a new switch port help --web <topic> could open the requested topic in the browser instead for users preferring websites over man pages.

Man pages will at least exist for all port commands, which will go into the man1 category. Some similar port commands should be covered by the same man page, such as activate/deactivate, archive/unarchive, etc. Splitting out certain topics from the current port(1) into their own man page to provide more details and examples will be considered; these will go into the man7 category.

Changes for base developers

As asciidoc is not available on Mac OS X systems without installing MacPorts we should not add it as a new dependency for building base. Therefore, the generated man pages will be checked into SVN in the same manner we already do for the configure script and other files generated by autoconf. Man pages will still reside in the base/doc directory.


Development Branch

These features will be developed on the new-help-system branch before being merged back to trunk. Depending on the progress of the manpage writing it will either target 1.8.0 or 1.9.0.

Current Status


Already done:


  • port-archive
  • port-build
  • port-cat
  • port-cd
  • port-checksum
  • port-clean
  • port-compact
  • port-configure
  • port-contents
  • port-dependents
  • port-deps
  • port-destroot
  • port-dir
  • port-distcheck
  • port-distfiles
  • port-dmg
  • port-dpkg
  • port-echo
  • port-ed
  • port-exit
  • port-extract
  • port-fetch
  • port-file
  • port-gohome
  • port-help
  • port-info
  • port-install
  • port-installed
  • port-lint
  • port-list
  • port-livecheck
  • port-load
  • port-location
  • port-mdmg
  • port-mirror
  • port-mpkg
  • port-notes
  • port-outdated
  • port-patch
  • port-pkg
  • port-platform
  • port-portpkg
  • port-provides
  • port-quit
  • port-rpm
  • port-search
  • port-select
  • port-selfupdate
  • port-srpm
  • port-submit
  • port-sync
  • port-test
  • port-trace
  • port-unarchive
  • port-uncompact
  • port-unload
  • port-upgrade
  • port-url
  • port-usage
  • port-variants
  • port-version
  • port-work


If those should be prefixed with port-* needs further discussion.

Already done:

  • (None)


  • macports.conf
  • sources.conf
  • variants.conf


Already done:

  • (None)


  • port-portfile
  • port-dev-style
  • port-dev-groups
    • port-dev-groups-python
    • port-dev-groups-perl
    • port-dev-groups-xcode
    • port-dev-groups-select
    • ...
  • port-hier
  • port-pseudo-ports
  • port-local-repository