| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
the WRKOBJDIR is set explicitly. This allows for having pkgsrc mounted
r/w without actually modifying it.
|
|
LIBTOOL_REQD to 1.5.18nb1.
|
|
and is still strong enough for pkgsrc use.
|
|
extract tools needed for the README.html generation. Suggested by
Johnny Lam and Rolland Illig.
|
|
define that inside double quotes.
|
|
Since replace.mk has its own loop to add dependencies, we can remove
the one from perl.mk.
|
|
tools known to the pkgsrc infrastructure.
|
|
mk/tools/perl.mk. This fixes broken dependencies on perl where the
path to the package wasn't defined.
|
|
variable definitions that apply when USE_IMAKE is defined.
|
|
to untar the archive.
|
|
(case-sensitive) to simplify writing the do-install target code that
automatically compresses or decompresses man pages after installation.
|
|
- completely redo the code which decides on the machine architecture,
operating system, and operating system version for the binary packages.
The old way just used to directory names to take a guess. The new
way creates a cache file containing meta-data for all the binary packages
in each "All" directory. This cache file is consulted when generating
the lists of available binary packages. The meta-data is obtained with
pkg_info so it should always be correct even if you do something silly
like mix OS_VERSION or MACHINE_ARCH packages up in the same directory.
Among the benefits are: works when PACKAGES is not $PKGSRC/packages,
works with a more or less arbitrary subdirectory structure, works
when there are subdirectories for multiple operating systems.
This portion of the fix should address PR25390.
The cache files are only updated when the contents of an "All" directory
changes or if the cache file format changes. There is some room for
improving the updating of the cache files, but its not too bad the way
it is.
- fix up some of the awk code so that generadme.awk works with Solaris
nawk as well as NetBSD's nawk and gawk (for pre-2.0 systems).
- remove some "if ! foo" shell constructs to increase portability.
- be more consistent with what variables get passed to mkreadme from
make and which ones are determined automatically. Mostly this meant
moving stuff into mkreadme to make it easier to run it standalone.
|
|
|
|
|
|
Also, rename "fuzz" to "fuzz_flags" to clarify that it's a set of flags
and should be used unquoted. Output from rilligd :)
|
|
because the <sys.mk> Makefile fragment sets CC?=gcc.
|
|
|
|
to note that we need the perl binary and the associated PERL5 and
TOOLS_PERL5 variable definitions.
|
|
|
|
patch cookie file, one per line. A package with no patches applied
will have a patch cookie file with no lines (zero bytes).
|
|
directory or the local patches directory exist. Also, emit the message
informing the user that pkgsrc patches are being applied that was lost
in the previous commit.
|
|
apply-distribution-patches and apply-pkgsrc-patches. Rewrite the
latter code to be more "whitespace-friendly" and to not need to invoke
${AWK} as many times. Drop support for PKGSRC_SHOW_PATCH_ERRORMSG
and simply always show the error message.
|
|
This makes it easy for people to track down which packages should receive
immediate attention.
|
|
TOOLS_CMD.* variables for the -2.13 variants. Otherwise, they're
empty, which causes errors for packages that use ${AUTOCONF}.
|
|
GNU tar archives. Create a new EXTRACT_USING value "nbtar" that causes
tar/ustar archives to be extracted using pax-as-tar, which understands
most GNU tar extensions. Default to EXTRACT_USING=nbtar, as quite a
few packages are distributed in GNU tar archives.
|
|
meaning.
|
|
specify that imake is used by the package, while the latter triggers
the special do-configure process.
|
|
|
|
the implication that the system yacc(1) is not good enough anyway.
|
|
framework. Problem & fix from tron@.
|
|
right in each variable, starting with the most generic one. Later
definitions override earlier ones. This makes the ``order'' testcase in
regress/pkg-options succeed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
which can take multiple values -- "pax" or "gtar". The default value
of EXTRACT_USING is "pax", which more closely matches reality since
before, we were using bootstrap "tar" for ${GTAR} and it was actually
pax-as-tar. Also, stop pretending pax-as-tar from the bootstrap kit
or on NetBSD is GNU tar. Lastly, in bsd.pkg.extract.mk, note whether
we need "pax" or "gtar" depending on what we need to extract the
distfiles.
|
|
|
|
comment for shlock.
|
|
|
|
"bison" and "bison-yacc". bison is just a symlink to the real bison,
but "bison-yacc" provides a "yacc" in ${TOOLS_DIR} that does "bison
-y". This allows the tools framework to provide everything that a
package might look for when asking for "bison" and avoids relying on
the bison being available in the PATH.
|
|
creating it in case ${MKDIR} can't handle that situation.
|
|
is already properly constructed to call the one in ${TOOLS_DIR}, which
symlinks to the correct make tools. From rillig@ in private mail.
|
|
From schwarz@ in private mail.
|
|
|
|
gzip.
|
|
Ditto for mailx. Lastly, /usr/bsd/zcat isn't gzcat (doesn't understand
gzipped files), so don't use it as a gzcat replacement. Changes from
Georg Schwarz in private email.
|
|
the final man pages to be compressed. If MANZ is not defined, then
we want the final man pages to be uncompressed.
We need to figure out if during installation, we need either gunzip
or gzip to decompress or compress the installed man pages. If a
package sets MANCOMPRESSED to "yes" or "no", then it's an indication
to the install code that the package itself installed the man pages
either compressed or uncompressed. If a package sets
MANCOMPRESSED_IF_MANZ, then the package uses BSD-style makefiles, so
we need to determine if the BSD-style makefile causes the man pages
to be compressed or not. In this case, we need to check in PKGMAKECONF
whether MANZ is set or not.
XXX Perhaps we should also check for MKMANZ if a package uses BSD-style
XXX makefiles?
|
