FreeBSD ports tree (read-only mirror)
3e4a05d81f
Feature Update ============== 1. Further update the --packages-build and --delete-build-only options to work with -a: a. Create a new function clean_build_only_list() from code that was already in dependency_check() and use it both there and at the end of the config mode in -a. b. Properly initialize the variables related to these two features in the same spot as all the other global vars are initialized rather than doing it in different locations. Major Cleanups ============== 1. 9-CURRENT has its own package repo now, hurray! 2. Instead of having a pca() to describe the post-config action collect the stuff that always runs after config is done into a function, and use the pca() logic to determine what to print. This also restores the whitespace to consistency between the modes (one port, multiport, -a). 3. Instead of fetching the directory listing for each port category (devel, ports-mgmt, etc.) every time we need to check a port, fetch it once and save it to a temporary file. This lets us do several cool things: a. Save a lot of time not having to re-fetch each iteration b. Run the sed code to fix %2c -> , up front c. Add a sed pattern to fix %2b -> + d. Run a variety of different patterns to try and find the latest_pv 4. We only want to run the logic tree on whether $latest_pv is up to date or not if that variable has a value, so add appropriate tests. Minor Cleanups ============== 1. Make it easier to include the --packages-build and --delete-build-only options in a portmaster rc file by setting the PM_BUILD_ONLY_LIST variable (which is used by both options) in the script if either of the two options is detected. 2. More robust error-handling for package directory creation in pm_pkg_create(). 3. Move the error message for "no package in -PP mode" to a variable for both reuse and code readability. Bug Fixes ========= 1. Not finding a package (or even a package repo) should only fail() if we are using -PP, not if we're just using -P. |
||
|---|---|---|
| accessibility | ||
| arabic | ||
| archivers | ||
| astro | ||
| audio | ||
| benchmarks | ||
| biology | ||
| cad | ||
| chinese | ||
| comms | ||
| converters | ||
| databases | ||
| deskutils | ||
| devel | ||
| dns | ||
| editors | ||
| emulators | ||
| finance | ||
| french | ||
| ftp | ||
| games | ||
| german | ||
| graphics | ||
| hebrew | ||
| hungarian | ||
| irc | ||
| japanese | ||
| java | ||
| korean | ||
| lang | ||
| math | ||
| mbone | ||
| misc | ||
| Mk | ||
| multimedia | ||
| net | ||
| net-im | ||
| net-mgmt | ||
| net-p2p | ||
| news | ||
| palm | ||
| polish | ||
| ports-mgmt | ||
| portuguese | ||
| russian | ||
| science | ||
| security | ||
| shells | ||
| sysutils | ||
| Templates | ||
| textproc | ||
| Tools | ||
| ukrainian | ||
| vietnamese | ||
| www | ||
| x11 | ||
| x11-clocks | ||
| x11-drivers | ||
| x11-fm | ||
| x11-fonts | ||
| x11-servers | ||
| x11-themes | ||
| x11-toolkits | ||
| x11-wm | ||
| .cvsignore | ||
| CHANGES | ||
| COPYRIGHT | ||
| GIDs | ||
| KNOBS | ||
| LEGAL | ||
| Makefile | ||
| MOVED | ||
| README | ||
| UIDs | ||
| UPDATING | ||
This is the FreeBSD Ports Collection. For an easy to use WEB-based interface to it, please see: http://www.FreeBSD.org/ports For general information on the Ports Collection, please see the FreeBSD Handbook ports section which is available from: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/ports.html for the latest official version or: The ports(7) manual page (man ports). These will explain how to use ports and packages. If you would like to search for a port, you can do so easily by saying (in /usr/ports): make search name="<name>" or: make search key="<keyword>" which will generate a list of all ports matching <name> or <keyword>. make search also supports wildcards, such as: make search name="gtk*" For information about contributing to FreeBSD ports, please see the Porter's Handbook, available at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/ NOTE: This tree will GROW significantly in size during normal usage! The distribution tar files can and do accumulate in /usr/ports/distfiles, and the individual ports will also use up lots of space in their work subdirectories unless you remember to "make clean" after you're done building a given port. /usr/ports/distfiles can also be periodically cleaned without ill-effect.