| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
individual defs.${OPSYS}.mk files. No change in functionality.
|
|
individual defs.${OPSYS}.mk files, and use them in bsd.pkg.mk.
+ _OPSYS_HAS_MANZ defines whether or not the OS does MANZ handling as standard
+ _PREFORMATTED_MAN_DIR is the name of directory (cat or man) where
preformatted manual pages go.
Rename the internal definitions used in the generation of PLIST files to
start with '_'.
This completes the "generic" changes to bsd.pkg.mk.
|
|
files, and use it in bsd.pkg.mk. This definition controls the fixup
of PLISTs at installation time, and running of ldconfig if necessary.
|
|
and use it in bsd.pkg.mk. This definition is the switch to patch(1) to
provide backup files when patching.
|
|
and use it in bsd.pkg.mk. This definition says whether or not the rpath
is to be added to the LDFLAGS definition.
|
|
files, and use it in bsd.pkg.mk. If set to "yes", checks that a valid
libintl library and header file should be performed.
|
|
files, defined to be the make program which is invoked by imake, and
use it accordingly in bsd.pkg.mk
|
|
files, rather than switching by ${OPSYS} within bsd.pkg.mk.
|
|
|
|
the package has been deleted.
|
|
|
|
the root user and root group.
|
|
but the user isn't prompted to customize the files at post-install time.
|
|
many of the tasks that need to be done when package is installed or
deinstalled:
* creating user/group for the package,
* creating and removing directories with special permissions and
ownership,
* copying config files to their final locations, and removing them
at deinstall time if they don't differ from the example ones,
* reminding the package admin of files he may want to customize or
of files/directories he may want to remove.
|
|
groups. These commands follow the basic interface of the NetBSD/Solaris
useradd and groupadd programs. For platforms on which these commands don't
exist, either sysutils/user is added as a dependency, or these are set to
${FALSE}, and the package admin is responsible for creating them himself
prior to the installation of a package.
|
|
config files should go. It may be overridden on a per-package basis by
defining CONFDIR.${PKGBASE}, e.g. CONFDIR.php. ${CONFDIR} defaults to
${PREFIX}/etc, but it may be overridden in /etc/mk.conf, e.g. by setting
CONFDIR=/etc.
Packages will eventually be altered to find their config files in
${CONFDIR}.
|
|
the moment.
|
|
|
|
|
|
that are concatenated together to form the whole MESSAGE file.
|
|
|
|
|
|
included, then it still points to a sensible location (${LOCALBASE}).
|
|
in ${.CURDIR} as well as ${PKGDIR}, just in case the pkg/ directory still
exists but is empty.
|
|
not bsd.pkg.mk, so that the user is more aware of them (there were placeholder
examples of both definitions in bsd.pkg.defaults.mk already).
Explain PRE_ROOT_CMD a bit more throroughly, and correct an example of
its use.
Make an alternative definition for SU_CMD sync with reality.
|
|
more speedups for building packages.
Get rid of a .USE macro, and do not spawn sub-makes for the pre-, do- and
post-target stages, replacing them with standard make(1) targets.
Timing information as follows (multiple runs performed, best results taken):
800 MHz Celeron, 128 MB, local pkgsrc, local obj
scripts/, pre,do,post-*: 0.731u 0.261s 0:02.04 48.5% 0+0k 29+168io 9pf+0w
no scripts/, pre,do,post-*: 0.678u 0.242s 0:01.30 70.0% 0+0k 0+169io 0pf+0w
no scripts/, no pre,do,post-*: 0.267u 0.089s 0:00.90 37.7% 0+0k 0+155io 0pf+0w
40 MHz Sparc, 36 MB, nfs pkgsrc, local obj
scripts/, pre,do,post-*: 22.590u 6.839s 0:33.31 88.3% 0+0k 121+254io 0pf+0w
no scripts/, pre,do,post-*: 22.481u 6.442s 0:33.30 86.8% 0+0k 120+251io 0pf+0w
no scripts/, no pre,do,post-*: 8.534u 4.189s 0:16.48 77.1% 0+0k 105+242io 0pf+0w
|
|
Makes the output a bit long at times but gives a nice concise idea of where
you're at and if the build is moving
|
|
whitespeace, followed by it's required pkgs. Make sure to look for that
whitespace, to not catch any wrong positives, e.g.
egrep "x11/kdebase.*" $DEPENDSFILE
will catch depends for both KDE1 and KDE2 and do weird things then (among
other things, think that kdelibs-2.2.1 is ok as a dependency when building
in x11/kdebase, which is certainly not!)
Eight broken pkgs less in the bulk builds by adding a single space!
(Now if adding some more would help further... :-)
|
|
no need to make "bulk-package" or "clean" after it!
|
|
lost.
However, modify previous change to let Darwin know about SHAREOWN,
SHAREGRP and SHAREMODE in a different way - no point in checking for
OPSYS here, since every OPSYS has to know about them.
|
|
|
|
|
|
russian-language ID3 tags as japanese-language ones.
Patch submitted by Sergey Svishchev <svs@ropnet.ru> in PR 14426.
|
|
these utilities in ${MKDIR}, ${RMDIR}, and ${TRUE}, so substitute for them.
|
|
Now the sed command is "s,#!.*/bin/perl,#!${PERL5},"
|
|
|
|
|
|
implicit `-print' action is performed on bar and not on foo. Surround
the search pattern in \( ... \) and add an explict -print so that all of
the results of the find are printed.
Problem noted and patch to fix this received in private email from Stoned
Elipot <seb@netbsd.org>.
|
|
@exec ${MKDIR} %D/...
instead of
@exec ${MKDIR} ${PREFIX}/...
Hopefully this might mean I don't commit incorrect PLISTs.
|
|
variables at once.
|
|
that GNU autoconf/automake are not executed during the build process, even
if the tools exist in the build environment. This prevents the build
process from overwriting any changes made to the configure script or to the
Makefile.in files.
|
|
set based on this choice if unset, and that blackdown-jdk13 is the default
on powerpc.
|
|
installed JVM to use to build java-based packages.
${JAVA_HOME} is not used to select where to install java based packages. All
packages which install java .jar files should install them in
${PREFIX}/lib/java, so that they will be accessible to multiple installed
JVMs.
|
|
scripts/{pre,post}-install - there is nothing that uses any of these,
and it incurs needless overhead.
|
|
${.CURDIR}/pkg directory to the toplevel of the package. It remains
backward compatible with the existing system allowing a progressive
transision process. The long term goal is a reduction of overheads and
processing time when working with the cvs tree.
|
|
the scripts/ directory, it will be run automatically as part of
the build process, by bsd.pkg.mk. There are now exactly 5 packages
in pkgsrc which use this facility, and yet, for every package build,
the existence of a script is checked by bsd.pkg.mk once before the
target is executed, and once afterwards. This incurs needless
overhead.
Move the separate pre- and post- script handling out of bsd.pkg.mk into
the individual package Makefiles, where it's much more obvious what is
happening, anyway.
|
|
of home grown post-patch target.
|
|
/usr/lib/crtbeginS.o and /usr/lib/crtendS.o make it into
{pre,post}dep_objects.
Fixes pkg/14353 from Witold J. Wnuk <witek@pd37.warszawa.sdi.tpnet.pl>
Tested as "still" working on 1.5.2.
Bump minor number of pkg and make pkgsrc depend on this version.
|
|
|
|
|
