| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
configure script.
|
|
- Sort dependencies properly so that, e.g., 2.10 is considered newer than 2.8.
This is still a hack and might fail in some cases, but is hopefully much
better than before.
|
|
|
|
use pkg-comment but have a COMMENT= in the Makefile.
|
|
|
|
|
|
|
|
|
|
|
|
* Check all the shell commands to see if they are mentioned in USE_TOOLS.
|
|
Not only CFLAGS, but also {FOO}_CFLAGS should be passed through the :M*
operator before being passed to the shell.
|
|
|
|
internal error showing up in benchmarks/netio.
|
|
reasonably well. In the first pass, all variables that are added to
BUILD_DEFS are collected, and in the second pass it is checked whether
any remaining user-defined variables are used but have not been added to
BUILD_DEFS. This way, it does not matter in which order the variables
appear in the files.
|
|
tiger instead. Also kill bogus NULL pointer handling in both algorithms:
passing null pointers as buffers (when len != 0) or context is a serious
programming error and should result in a segfault. Bump version to
20060826. OK agc@
|
|
shell parser to correctly handle ${WRKSRC.${d}}, which appears for
example in geography/epsg.
Avoided an internal fatal error for files that contain RCS conflicts.
|
|
|
|
|
|
- Intoduce fatal_later() and fatal_later_check() and use them to clean
up reporting unavailable package dependencies
- Remove unused references to opt_S (reported by bad@)
- Fix manpage reference DEPENDS_TARGET -> UPDATE_TARGET (reported by bad@)
|
|
|
|
Correct installation logic -- it was reversed.
Bump version number, since package was completely broken.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"Deprecated options" part of the manual.
PR#34145 by Dieter Roelants.
|
|
Changes since 4.67:
- Adjusted to the ongoing changes in the pkgsrc infrastructure.
- Many small improvements in the makevars.map file.
- Stricter checking of dependency patterns, to catch foo-*.
- Small improvement on the use of stack space due to complicated regular
expressions.
- Many more absolute pathnames are found in patch files, no matter which
type of file is patched.
- All user-defined variables that are used should be added to BUILD_DEFS.
- All packages that set GNU_CONFIGURE are assumed to need a C compiler.
- Instead of ${TOOL}, tool may be used directly, since the tool wrappers
are installed very early in the build process.
- Removed the --debug option.
... and many more.
|
|
in double quotes or not, inside backticks.
|
|
|
|
|
|
IMAKE_MAKE replaced in pkgxmkmf.
|
|
Approved by wiz@.
|
|
which helps for some Perl modules to get the correct package name, which
in turn influences whether the update requests from doc/TODO can be
shown or not.
Suggested by wiz.
|
|
|
|
absolute pathnames.
|
|
some of the infrastructure files. This also allows checking the
Makefiles in htdocs.
Added GAMEOWN, GAMEGRP and GAMEDIRMODE to the list of user-defined
variables that don't need to be mentioned in BUILD_DEFS.
When looking for absolute pathnames in "other" files, don't require them
to have a second component. This produces warnings for /var and /tmp,
which had been hidden before.
When strings that are likely to be absolute pathnames appear in the form
$(VARIABLE)/bin or "+ '/bin'", don't print a warning. The latter is used
when "+" is a string concatenation operator.
The direct use of tools is only suggested in targets named
{pre,do,post}-*, since other ones may be invoked without the tool
directory being in the PATH.
|
|
|
|
saved in the line as extra fields.
When checking for absolute pathnames in "other" files, allow the form
${variable}/bin, as seen in www/apache2/patches/patch-ad. Noticed by
Matthias Scheler.
|
|
if requested. Suggested by Joerg Sonnenberger.
|
|
|
|
|
|
|
|
|
|
-D... options.
Removed the check for the :Q operator in C preprocessor macro
definitions, since we generally don't expect directory names with
embedded special characters in pkgsrc.
In buildlink3.mk files, the only BUILDLINK_* variables that may be set
are those of the current package.
The shell variables $@ and $? are now recognized. Since the shell parser
is able to parse the complete code in all pkgsrc packages, make parse
errors show in the normal pkglint output. These errors had been hidden
before.
Fixed the regular expressions in the shell parser to only match at the
beginning of the string. That way, when the shell command contains $$@,
the $@ is not removed, leaving a single $ behind.
Added some code to deal with the different parsing styles of bmake in
variable assignments and shell commands. For that, the PkgLint::Line
class has been extended to contain arbitrary additional data. This will
also allow to reduce the number of duplicate warnings later.
The assert() procedure has got a second parameter, the message to be
printed.
Variable assignment lines start start with a space character (\u0020)
are now recognized, but no warning is printed.
In pathnames and pathmasks, the '#' character is allowed, since some
packages need to remove the .#* files from CVS before installing.
|
|
|
|
install phase.
Stricter checks for manual pages in PLIST files.
|
|
- Resolve PR/31909 - use tr rather than fmt to avoid issue on Solaris
- Resolve PR/33370 - always show fatal messages to STDERR
- Resolve PR/32326 - Correctly extract PKG_DBDIR
Also, when -v is used display the state of all extracted variables at the
start of the run
|
|
simple commands (for example "cp") should be used, since the tools
framework provides wrappers for them. This applies only to the cases
where the tool variables appears as the first word in a shell command.
When doing substitutions in files that are later installed, the full
name should still be used.
|
