Skip to content
  • kris's avatar
    - Allow processing of info files in non-standard locations; the · e2d890ce
    kris authored
      INFO_PATH variable may be used to specify their location.  It defaults
      to 'share/info' for the standard PREFIX, and 'info' when PREFIX ==
      /usr. [1]
    
    - Remove the <category>/pkg/COMMENT files in favour of a COMMENT
      variable in <category>/Makefile [2]
    
    - Prevent patch breakage with VERSION_CONTROL=numbered [3]
    
    - Fix some instances of incorrect WRKDIRPREFIX handling. [4]
    
    - remove useless ${MKDIR} ${WRKSRC} in config target [5]
    
    - remove reference to OpenBSD [6]
    
    - Exempt devel/p5-Module-Build from the self-dependency in
      PERL_MODBUILD so that this port may use the option without getting an
      infinite dependency list [7]
    
    - The default PERL_ARCH is currently determined as a function of
      OSVERSION. It should however be a function of PERL_LEVEL since the
      correct value depends on what Perl version one has installed (older
      Perl versions use ${ARCH}-freebsd, newer versions use mach). [8]
    
    - Fix PORTDOCS on older (4.7, 5.0) systems [9]
    
    - Allow 'make parallel' to generate a working makefile when not all
      categories are present (this does not mean you'll be able to build all
      ports, unless you make sure they don't have external dependencies) [10]
    
    - Don't report symlinks as world-writable in the security check [11]
    
    - Fix a comment that was broken by a mismerged patch [12]
    
    - Clarify the meaning of USE_*, WANT_*, WITH_* and WITHOUT_* [13]
    
    - Don't set _CHKSUMFILES/_IGNOREFILES if CKSUMFILES/IGNOREFILES is
      empty and DIST_SUBDIR is set. [14]
    
    - Fix comment for DISTDIR [15]
    
    - Update the documentation of the USE_GL variable [16]
    
    - Check to see if NONEXISTENT exists, and fail with an error if it does [17]
    
    - Fix fetching of new distfiles in 'make makesum' when SIZE is set [18]
    
    - Consistently set MAKE_ENV when USE_GCC=3.2 or 3.3 are set [19]
    
    - Rework INDEX builds: [20]
    
      * Fix the bsd.port.subdir.mk code that is supposed to report index
        breakage (the fallback code wasn't actually being run because make
        would halt immediately following the error).  This should help with
        INDEX error reports because it will immediately show the cause of
        failure, so we won't have to pull teeth to extract it from the
        submitter.
    
      * Streamline the 'make describe' code a bit.
    
      * Provide some basic instructions to the user when an index build
        fails, on when and how to report index build failures (turn this off
        with INDEX_QUIET=1)
    
      * Removed INDEX_NOSORT, because I couldn't imagine it to be very
        useful and it doesn't cost very much anyway.
    
      * Don't prevent INDEX builds from seeing the local host environment.
        Since a lot of users are using 'make index' thesedays they should get
        an index that reflects their local settings and installed ports.  If
        you want to build a 'default' index that isn't influenced by local
        settings (e.g. for release builds), set the INDEX_PRISTINE variable.
    
      * Allows parallel INDEX builds (using make -j).  The most obvious way
        of doing this doesn't work, because I/O from child makes is broken up
        into 2k chunks, and output lines from 'make describe' that exceed this
        length (*cough* GNOME *cough*) will be intertwined with the output of
        other makes, leading to a corrupted INDEX.  The I/O interleaving
        can be disabled using 'make -P', but this inserts extraneous output of
        its own, and redirects stderr, making it useless for our purposes.
        Instead, I collect the output from the child make processes in
        temporary files and recombine them at the end.
    
      * The number of concurrent make processes to spawn can be set using
        INDEX_JOBS.  By default this is set to 2, which seems to be a sweet
        spot for both single and dual-processor systems.  On my tests I do not
        see any significant performance changes on UP, but on a dual 4.x
        system the build time drops by 47% (6 minute index builds on one test
        machine!).  Depending on your disk and CPU hardware you might see
        further gains with INDEX_JOBS=4 or higher, so you might like to
        experiment to see what works best.  On a dual 5.x system the
        performance gains do not seem to be as great (20-30%), but this is
        still a significant net win.
    
    PR: 		55493 [1], 59651 [2], 61552 [3], 62247 [4], 62329 [5],
    		62337 [6], 62422 [7], 62441 [8], 62627 [9], 62983 [10],
    		63112 [11], 63297 [12], 63335 [13], 64029 [14], 64069 [15],
    		64236 [16], 64519 [17], 62958 [18], 64237 [19]
    
    Submitted by:	lev [1],
    		Matthew Seaman <m.seaman@infracaninophile.co.uk> [2],
    		Joel Ray Holveck <joelh@piquan.org> [3],
    		ade [4], Sergey Matveychuk <sem@ciam.ru> [5],
    		markus [6], mat [7], des [8], eik [9],
    		Dmitry Morozovsky <marck@rinet.ru> [10],
    		Andrew <andrew@ugh.net.au> [11], vs [12], linimon [13],
    		edwin [14][15], gerald [16], marcus[17][18], kris [19][20]
    e2d890ce