Subject: Re: proposal 5: flexible distfile handling
To: Todd Vierling <>
From: Hubert Feyrer <>
List: tech-pkg
Date: 05/27/1999 14:57:29
On Fri, 21 May 1999, Todd Vierling wrote:
> - [replaces PATCHDIR]
>   PATCHDIRS:  A list of directories containing patch files for this package.
>   ALWAYS includes ${.CURDIR}/patches, if it exists.  Specializations of
>   ${.CURDIR}/patches based on ${OPSYS}, ${MACHINE_ARCH}, or ${OS_VERSION}
>   are removed for cleanliness (their application can be replaced by
>   appropriate conditionalization inside the patches).  Patch names in these
>   directories must match the pattern "patch-*".
Is there a particular reason for insisting on filename (other to get
sort-order for applying them)? I've added several patches from PRs, and
thought it would have been nice to add them as patches/pr-1234, so one
knows where they come from whem looking at them, or to denote some
filename that they patch, without lookint into the patch first.

> - MASTER_SITES:  May contain directory URLs, as currently used, which will
>   be applied to all of DISTFILES and PATCHFILES.  May also contain entries
>   of the form:
>     GLOB=URL
>   where GLOB is a csh(1) style glob pattern and URL is a directory URL.
>   While iterating the DISTFILES list at fetch time, entries in MASTER_SITES
>   with a GLOB must match the distfile in order to use that URL for fetching.

Um, can you give some examples here? 
Is this to say "only fetch these few files from there"?

 - Hubert

NetBSD - Better for your uptime than Viagra