Age | Commit message (Collapse) | Author | Files | Lines |
|
LIBTOOL_OVERRIDE steps into a separate do-libtool-override target. Create
a new variable _CONFIGURE_POSTREQ that currently lists do-libtool-override.
Also add some documentation for the two _CONFIGURE_* variables:
_CONFIGURE_PREREQ is a list of targets to run after pre-configure but before
do-configure. These targets typically edit the files used by the
do-configure target.
_CONFIGURE_POSTREQ is a list of targets to run after do-configure but before
post-configure. These targets typically edit the files generated by
the do-configure target that are used during the build phase.
|
|
"replace-perl", instead of keeping it as part of the do-patch target. Now,
a "make patch" will result in just the patched sources.
|
|
descriptive. There is a separate step to replace the actual libtool script
that is controlled by LIBTOOL_OVERRIDE within the "do-configure" target.
|
|
document it and USE_CURSES in Packages.txt anymore (packages should
really use devel/ncurses/buildlink.mk instead).
|
|
|
|
|
|
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
|
|
(even though that's still a bad idea), set USETOOLS=no explicitly before
including <bsd.own.mk>, and add this also to MAKE_ENV to make BSD-Makefile
based packages build properly.
|
|
use to set PKGBASE, which is used in the name of the package-specific
config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if
PKGNAME wasn't explicitly set in the package, then the override would not
work.
|
|
directory.
|
|
executed outside of a package directory. Problem and fix noted by Stoned
Elipot in private email.
|
|
|
|
|
|
PKG_USERS represents the users to create for the package. It is a
space-separated list of elements of the form
user:group[:[userid][:[descr][:[home][:shell]]]]
Only the user and group are required; everything else is optional,
but the colons must be in the right places when specifying optional
bits. Note that if the description contains spaces, then spaces
should be double backslash-escaped, e.g.
foo:foogrp::The\\ Foomister
PKG_GROUPS represents the groups to create for the package. It is a
space-separated list of elements of the form
group[:groupid]
Only the group is required; the groupid is optional.
This solves the problem of what to do when there is more than one user or
group needed for a package, e.g. qmail. Also add a bit more error-checking
to the INSTALL/DEINSTALL scripts.
|
|
the shell doesn't like.
Fixes PR 14347 by Ben Wong <Benjamin.Wong@cc.gatech.edu>
|
|
now work on Darwin, and then the discussion about allowing spaces in
user/group names, make these scripts work even if the inputs contain
spaces. Yes, this is overkill, but after doing all of the work, I didn't
want to waste it.
|
|
re-indent for aesthetic considerations.
|
|
to prevent it sitting there for days waiting for input in useless
situations.
|
|
Hubert Feyrer.
|
|
|
|
accordingly so that config files are in /usr/pkg/etc/foo.conf, and not
/usr/pkg/etc//foo.conf.
|
|
|
|
to bsd.pkg.obsolete.mk.
|
|
still to be used. These may eventually disappear over time as the contents
are, by definition, obsolete and deprecated.
|
|
|
|
This value may be customized in various ways:
PKG_SYSCONFBASE is the main config directory under which all package
configuration files are to be found.
PKG_SYSCONFSUBDIR is the subdirectory of PKG_SYSCONFBASE under which the
configuration files for a particular package may be found.
PKG_SYSCONFDIR.${PKGBASE} overrides the value of ${PKG_SYSCONFDIR} for a
particular package.
Users will typically want to set PKG_SYSCONFBASE to /etc, or accept the
default location of ${PREFIX}/etc.
This obsoletes the use of CONFDIR, which was active for only 6 days, so no
need to have a workaround to still accept old CONFDIR settings.
|
|
so that the general INSTALL/DEINSTALL scripts can manage these extra files
and directories.
|
|
|
|
|
|
|
|
"curses" because the first deals with resize better, especially under
NetBSD 1.5/1.5.x. This change was suggested by Joe Abley in PR pkg/13630.
|
|
remove the temporary ${PKGDIR} workaround.
|
|
|
|
names of the scripts and is no longer a MLINKS-type variable. The scripts
are copied into ${RCD_SCRIPTS_DIR} which defaults to /etc/rc.d for now.
It's unclear if Linux/Solaris would set RCD_SCRIPTS_DIR to something else.
|
|
defs.${OPSYS}.mk files.
|
|
files, and use it in ossaudio.buildlink.mk. The definition shows whether
or not libossaudio is available in the OS.
|
|
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.
|