Age | Commit message (Collapse) | Author | Files | Lines |
|
This halts the execution if an installed package's object format is not
the same as the object format currently in use. It can be set to "no" on
the rare occasion where the interface to the pre-requisite packages is one
of a binary, not a library.
|
|
When an installed package is found as part of a DEPENDS pre-requisite,
check its object format. If there is none in the installed package,
that package was probably built before 29th September 1999, which was
when the OBJECT_FMT definition was added to the BUILD_DEFS, so print a
warning and continue. If the object format of the installed package
and ${OBJECT_FMT} are the same, then continue. If the object format
of the installed package and ${OBJECT_FMT} differ, then print an error
message explaining the error, and exit.
|
|
for users to choose their own JVM.
USE_JAVA sets up DEPENDS and $JAVA_HOME appropriately, based on PKG_JVM.
Currently sane values of PKG_JVM are `jdk' and `kaffe', where the default
is `jdk' on NetBSD-*-i386, and `kaffe' elsewhere.
|
|
expansion, instead of letting sh(1) DTWT.
Noted by Kazuki Sakamoto <sakamoto@cec.co.jp>
|
|
|
|
1999, so make that the date for the test, not 9th September 1999.
|
|
match more than one package, and warn about it:
*** WARNING: Dependency on 'gnome-*' expands to several installed packages
( gnome-libs-1.0.53 gnome-core-1.0.53 gnome-print-0.9 ).
Please check if this is really intended!
In such a case, the pattern ('gnome-*') should be tightened to only match
what's really intended (e.g. 'gnome-[0-9]*').
|
|
$DEPENDS with wildcards and relational depends possible. (The previous
solution with :Q was not useful as this also quoted the seperator between
the single depends, making the DEPENDS useless).
|
|
by the shell.
|
|
Make the print-pkg-size target work on Solaris if there are no
pre-requisite packages.
|
|
(Need to test PKGTOOLS_VERSION, not PKGTOOLS_REQD, to see if the new code
is present; for PKGTOOLS_VERSION to get defined, some code needs to get
moved around a bit, though)
|
|
additional make call), and pass it in the environment to any
recursive make calls. 'make fetch' in gnumeric on my system is now
> 15% faster checking dependencies.
|
|
|
|
fixes pr 9106 by abs@netbsd.org.
|
|
|
|
target to create the PLIST on the fly. (This is just an alias for the
existing ${PLIST} target, but with that you have to type the full path
which is inconvenient).
|
|
|
|
|
|
|
|
|
|
miyu% make
===> xephem-3.1 Unacceptable license: no-commercial-use.
To build this package, add this line to your /etc/mk.conf:
ACCEPTABLE_LICENSES+=no-commercial-use
To do this, we need to change the semantics of the IGNORE variable. It is
no longer taken as one variable, but rather as one variable with several
lines, seperated by whitespace. Each line will be printed on it's own.
In addition, the code for the IGNORE_FAIL has been slightly moved around
so IGNORE_SILENT can be used together with IGNORE_FAIL now. (does someone
use this?).
|
|
|
|
|
|
substitute pkglibtool for the pkg's own libtool.
"ltconfig" is script to make "libtool" script.
"ltconfig" is executed by GNU's "configure" script at
"do-configure" target.
if USE_LIBTOOL and LTCONFIG_OVERRIDE defined, specified "ltconfig"
is overrided to symlink pkglibtool to "libtool" instead of making
"libtool" before executing "configure".
if USE_LIBTOOL and LIBTOOL_OVERRIDE defined, specified "libtool" is
removed, and symlinked from pkglibtool after executing "configure"
(and "ltconfig").
|
|
|
|
|
|
are set.
|
|
installed version and binary packages. The size can be queried then
via pkg_info:
xfeyrer @ noon% pkg_info -s xv
Information for xv-3.10apl1:
Size of this package in bytes: 4670692
xfeyrer @ noon% pkg_info -S xv
Information for xv-3.10apl1:
Size in bytes including required pkgs: 14610165
While doing work on the size code, support for the @src directive was
removed (formerly enabled with the pkg_create -s switch, but unused in
our pkg system). The new pkg_info -s and -S switches were tested on
installed, local (file) and remote (ftp) packages.
In bsd.pkg.mk, take special care for pkg_* versions that do not have
the pkg_create -s and -S switches and do not record size information
there.
|
|
|
|
specifies flags in PKG_FC, they are properly handled.
|
|
|
|
USE_FORTRAN should be set in the package Makefile. The logic added by this
commit will choose a fortran compiler to use and set the correct dependency
rather than having this selection scattered across each package which needs
a fortran compiler.
- Add PKG_FC variable. By setting PKG_FC in /etc/mk.conf, users can force the
selection of which fortran compiler gets used by the package system. If not
specified, PKG_FC defaults to f2c-f77 on pre-1.4 systems that did not include
/usr/bin/f77. In addition PKG_FC defaults to f2c-f77 on newer systems since
f77 is still somewhat buggy. When /usr/bin/f77 becomes more stable, the
default should be changed from f2c-f77 to f77.
|
|
whitespace - don't duplicate the whitespace.
|
|
|
|
MASTER_SITE_BACKUP doesn't end in //.
For this, any setting of MASTER_SITE_LOCAL in /etc/mk.conf must no longer
include ${DIST_SUBDIR} - this will be added automatically, if needed.
|
|
space (make(1) interprets leading tabs as the prefix denoting a shell
command).
|
|
this license is used by graphics/cqcam and mail/sendmail pkgs.
Suggested by Bjoern Labitzke <hermit@labitzke.isdn.cs.tu-berlin.de>.
|
|
ftp://sunsite.sut.ac.jp/pub/archives/linux/sunsite-unc/
|
|
|
|
|
|
Patch from NoRM <norm@mono.org>
|
|
|
|
in a package patch.
|
|
if patch(1) is smart enough (i.e. not Solaris by default). Also
introduce a second patch stage (in the package patch phase, not the
distribution patches), whereby a misapplied patch with
${PATCH_FUZZ_FACTOR} will be tried again without a fuzz factor. This
will fail on package patches which patch many files, but these should
be fixed anyway.
|
|
has a patch(1) that doesn't recognise a fuzz-factor option.
Pointed out by Frank van der Linden.
|
|
|
|
picked up from a different directory (typically, this is /usr/dt on
Solaris).
|
|
PLIST, as shared objects. Tested with both GNU egrep and Solaris XPG4
egrep. Not the most compact of regular expressions, due to
non-portability of {n,m} repetition atoms between different versions
of egrep.
|
|
Here is a summary of the changed behaviour:
* A "make update" will no longer clean the subtree before running.
* If called a second time, it will resume package installation, in
case a previous "make update" was interrupted for some reason.
(just make sure you don't call "make clean" in between ;-)
* Unless "NOCLEAN" is set, "make update" will clean up the subtree
after successfully updating _all_ packages (to avoid a dirty directory
structure for future makes).
* A "clean-update" target has been introduced to clean up the subtree
that gets updated. This should be used prior to an initial "make
update" if you suspect that one of the packages that get updated may
be dirty.
XXX: this still does not automatically check for or update any obsolete
´upstream' packages (e.g., if gtk depends on glib, a "make update"
in the gtk directory won't automatically update glib, you have to
do it the other way round).
|
|
- substitute leading tabs with spaces in IRRD_USE_PGP comment
- use ``YES'' instead of ``yes'' for appropriate variables
- move GLX_CHIPSET, INN_DATA_DIR and KNEWS_* so that the variables are sorted
alphabetically
- add description of possible values for USE_GIF
- comment out NMH_MTA (nmh Makefiles DTRT)
- append = to variables as appropriate so that make(1) will parse them
correctly if they are uncommented
Other minor cleanups:
- s/set, not set/defined, not defined/ in comments
- use empty value consistently for variables whose only purpose is to
be either defined or undefined (previously, either ``yes'', ``1'' or
empty value was used)
- mark variable UVM as obsolete (XXX it should be g/c'ed probably)
|