${WRKDIR} every time with "mkdir -p" - instead, use the ${WRKDIR}
target, so that any symlinks to it are created properly.
Also, when creating the ${DLIST} file in the update target, don't pipe
the output of pkg_info -R through "tail -n +4" - simply use pkg_info -qR
to achieve the same results.
GENERATE_PLIST is a sequence of commands, terminating in a semicolon,
that outputs contents for a PLIST to stdout and is appended to the
contents of ${PLIST_SRC}.
Convert the perl5 packlist handling to use GENERATE_PLIST.
- remove unwanted entries earlier by using ${GREP} -v
- substitute more specific bits before lesser ones: ${MACHINE_GNU_PLATFORM}
before ${MACHINE_ARCH} and ${MACHINE_GNU_ARCH}
- substitute *after* the sort so substitution does not move the
pathnames around
- add substitution of ${PKGVERSION}
- substitute ${PKGLOCALEDIR}/locale (this can help actually catching PLIST,
configuration, build, ... problems with respect to the correct locale
directory varying from platform to platform)
Enable this package for all platforms.
Added GAWK_ENABLE_PORTALS to mk/bsd.pkg.defaults.mk to enable/disable gawk
handling file names that start with `/p/' as a 4.4 BSD type portal file.
Changes from 3.0.4 to 3.0.5:
- bug fix release only.
Changes from 3.0.5 to 3.0.6:
- bug fix release only.
Changes from 3.0.6 to 3.1.0:
- A new PROCINFO array provides info about the process. The non-I/O /dev/xxx
files are now obsolete, and their use always generates a warning.
- A new `mktime' builtin function was added for creating time stamps. The
`mktime' function written in awk was removed from the user's guide.
- New `--gen-po' option creates GNU gettext .po files for strings marked
with a leading underscore.
- Gawk now completely interprets special file names internally, ignoring the
existence of real /dev/stdin, /dev/stdout files, etc.
- The mmap code was removed. It was a worthwhile experiment that just
didn't work out.
- The BINMODE variable is new; on non-UNIX systems it affects how gawk
opens files for text vs. binary.
- Gawk no longer supports `next file' as two words.
- On systems that support it, gawk now sets the `close on exec' flag on all
files and pipes it opens. This makes sure that child processes run via
system() or pipes have plenty of file descriptors available.
- If `--posix' is in effect, newlines are not allowed after ?:.
- Weird OFMT/CONVFMT formats no longer cause fatal errors.
- Diagnostics about array parameters now include the parameter's name,
not just its number.
- It is now possible to open a two-way pipe via the `|&' operator.
See the discussion in the manual about putting `sort' into such a pipeline,
though. (NOTE! This is borrowed from ksh: it is not the same as
the same operator in csh!)
- The close() function now takes an optional second string argument
that allows closing one or the other end of the two-way pipe to
a co-process. This is needed to use `sort' in a co-process, see
the doc.
- If TCP/IP is available, special file names beginning with `/inet'
can be used with `|&' for IPC.
- With `--enable-portals' on the configure command line, gawk will also
treat file names that start with `/p/' as a 4.4 BSD type portal file,
i.e., a two-way pipe for `|&'.
- Unrecognized escapes, such as "\q" now always generate a warning.
- The LINT variable is new; it provides dynamic control over the --lint
option.
- Lint warnings can be made fatal by using --lint=fatal or `LINT = "fatal"'.
Use this if you're really serious about portable code.
- A number of lint warnings have been added. Most notably, gawk will
detect if a variable is used before assigned to. Warnings for
when a string that isn't a number gets converted to a number are
in the code but disabled; they seem to be too picky in practice.
Also, gawk will now warn about function parameter names that shadow
global variable names.
- It is now possible to dynamically add builtin functions on systems
that support dlopen. This facility is not (yet) as portable or well
integrated as it might be. *** WARNING *** THIS FEATURE WILL EVOLVE!
- Profiling has been added! A separate version of gawk, named pgawk, is
built and generates a run-time execution profile. The --profile option
can be used to change the default output file. In regular gawk, this
option pretty-prints the parse tree.
- Gawk has been internationalized, using GNU gettext. Translations for
future distributions are most welcome.
- New asort() function for sorting arrays. See the doc for details.
- The match function takes an optional array third argument to hold
the text matched by parenthesized sub-expressions.
- The bit op functions and octal and hex source code constants are on by
default, no longer a configure-time option. Recognition of non-decimal
data is now enabled at runtime with --non-decimal-data command line option.
- Internationalization features available at the awk level: new TEXTDOMAIN
variable and bindtextdomain() and dcgettext() functions. printf formats
may contain the "%2$3.5d" kind of notation for use in translations. See
the texinfo manual for details.
- The return value from close() has been rationalized. Most notably,
closing something that wasn't open returns -1 but remains non-fatal.
- The array effeciency change from 3.0.5 was reverted; the semantics were
not right. Additionally, index values of previously stored elements
can no longer change dynamically.
- The new option --dump-variables dumps a list of all global variables and
their final types and values to a file you give, or to `awkvars.out'.
- Gawk now uses a recent version of random.c courtesy of the FreeBSD
project.
- The gawk source code now uses ANSI C function definitions (new style),
with ansi2knr to translate code for old compilers.
- `for (iggy in foo)' loops should be more robust now in the face of
adding/deleting elements in the middle; they loop over just the elements
that are present in the array when the loop starts.
This is mostly to get the improved/fixed version number handling provided
by this version of the tools, but see the log of
pkgsrc/pkgtools/pkg_install/Makefile revision 1.47 for a summary of
changes.
+ Check for the existence of pkg_tarup, and fail if it can't be found.
+ Place the binary package of the replaced-package in the ${WRKDIR},
rather than overwriting any instance in ${PKGREPOSITORY}.
+ Don't make a binary package when undoing the replacement.
libraries the following could occur
- a.out platforms: c++rt0.o would be missing and therefore
global contstructors would not work.
- ELF platforms libstdc++ and libm would not be explicitly
linked in.
This affected notably libqt and explains the build failure of kdelibs2 on
arm32.
Bump PKGREVISION and require it.
fails because otherwise the next invokation of the "update" target will
not attempt to remove the package again. Fix provided by Aaron J. Grier
in PR pkg/15827.
${X11BASE} instead of checking for -I or -L in front of it. This is okay
because ${BUILDLINK_X11_DIR} should just never appear in any installed
files regardless of its prefix. Problem noted in private email by Mark
Davies <mark@mcs.vuw.ac.nz>.
$${file} is a libtool archive (*.la). It allows libtool to properly
interact with buildlink at link time by linking against the libraries
pointed to by symlinks in ${BUILDLINK_DIR}.
This change has been tested by me on NetBSD-1.5ZA/i386 and by Mark
Davies <mark@mcs.vuw.ac.nz> on Solaris.
a.out but are now ELF, in a way that's consistent with bsd.own.mk in
NetBSD-current. This, incidently, makes the gcc package build again on
NetBSD-1.5.3_ALPHA/i386.
the package revision added. Replace "PKGNAME" in package list with this
value because the installed software doesn't know anything about package
system revision. This fixes package list problems in e.g. the "xemacs"
package.
We *must* record the version of "${.CURDIR}/Makefile" because we otherwise
only record the version of the wrong "Makefile" e.g.
"x11/xscreensaver-gnome/../xscreensaver/Makefile" for the
"xscreensaver-gnome" package. This will break the update target horribly.
When constructing the build version information, avoid problems
when there is a filename with an embedded space in the directory.
With thanks to Stoned Elipot for the practical help.
- - For "fetch", move the assignment of the "getsite.sh" script to a more
natural place, to get the full benefit of, and consistent handling for,
setting MASTER_SORT and MASTER_SORT_REGEX
- - For "fetch-list", embed the "getsite.sh" script into the generated
script, so that the calculation can be properly done at run-time.
("fetch-list" also respects MASTER_SORT and MASTER_SORT_REGEX.)
