HaikuPorts
  • Login
  • Preferences
  • Help/Guide
  • Wiki
  • Timeline
  • Roadmap
  • View Tickets
  • Search
  • Port Log
  • Blog
wiki:HaikuPorterForPM/Usage

Context Navigation

  • ← Previous Version
  • View Latest Version
  • Next Version →


Version 1 (modified by zooey, 2 years ago) (diff)

--

Usage

Options

In order to see the available options, please invoke haikuporter --help

Usage: haikuporter [options] portname[-portversion]

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit
  -l, --list            list available ports
  -a, --about           show description of the specified port
  -s, --search          search for a port (regex)
  -o, --location        print out the location of a recipe (via search, for
                        scripted editing)
  -q, --quiet           suppress output from build actions
  -y, --yes             answer yes to all questions
  -j JOBS, --jobs=JOBS  the number of concurrent jobs to build with
  -S, --strict-policy   require strict packaging policy adherence; packaging
                        will fail on any policy violation
  -n, --nopatch         don't patch the sources, just download and unpack
  -e, --extract-patchset
                        extract current patchset(s) from port source(s)
  -G, --init-git        create git-repo(s) for port source(s)
  -B, --patch-files-only
                        don't build the port, just download, unpack and apply
                        patch files; don't call PATCH() though
  -b, --nobuild         don't build the port, just download, unpack and patch
  -p, --nopackage       don't create package, stop after build
  --nosrcpackage        don't create a source package by default
  --test                run tests on resulting binaries
  -C, --nochroot        build without a chroot()-environment - meant for
                        debugging the build/install process
  -f, --force           force to perform the steps (unpack, patch, build)
  -F, --preserve-flags  don't clear any flags when a changed recipe file is
                        detected
  -P PORTSFILE, --portsfile=PORTSFILE
                        handle all ports in the given file
  -w WHY, --why=WHY     determine why the given port is pulled in as a
                        dependency of the port to be built
  -D, --analyze-dependencies
                        analyze dependencies between ports and print
                        information; no port parameter required
  -c, --clean           clean the working directory of the specified port
  -g, --get             get/update the ports tree
  -t, --tree            print out the location of the haikuports source tree
  --lint                scan the ports tree for problems

Download in other formats:

  • Plain Text

Trac Powered

Powered by Trac 0.13dev-r10686
By Edgewall Software.

Visit the Trac open source project at
http://trac.edgewall.org/