summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2002-10-11Remove NS_INST variable, obsoleted by last changes to www/netscape7jschauma1-6/+1
2002-10-09* Modify example buildlink2.mk: we now also want a variable calledjlam1-5/+15
BUILDLINK_PKGBASE.<pkg> that is the ${PKGBASE} for that package and can be used as "pkg_info ${BUILDLINK_PKGBASE.<pkg>}". This variable is currently only used if the buildlink2.mk file uses BUILDILNK_PLIST_CMD.<pkg> (described below). * Create readable variable BUILDLINK_PLIST_CMD.<pkg> that is a pipeline of shell commands that outputs to stdout a list of the files installed the <pkg>, relative to its installation prefix.
2002-10-09Rearrange _BUILDLINK_USE target code a bit to allow for BUILDLINK_FILESjlam1-4/+5
to be a shell command, e.g.: BUILDLINK_FILES= `cd ${LOCALBASE}; ${LS} -1 lib/libfoo.*`
2002-10-09* Create variables BUILDLINK_CPPFLAGS and BUILDLINK_LDFLAGS that arejlam1-7/+24
readable through CONFIGURE_ENV and MAKE_ENV. These may be used to fix up packages that use imake to check the appropriate locations for headers and libraries. * Don't be so aggressive in prepending _BLNK_{CPP,LD}FLAGS to {C,CPP,CXX,LD}FLAGS. The buildlink2 wrapper scripts will automatically filter out bad -[IL] paths, even if their added inadvertantly by package Makefiles, so we can simply append them to the existing {C,CPP,CXX,LD}FLAGS. We try to be smarter about appending them to avoid needless duplication.
2002-10-09Allow BUILDLINK_ENV to override shell environment settings injlam1-1/+8
${CONFIGURE_ENV} and in ${MAKE_ENV} for the configure and build processes, respectively. This allows overriding the value of "CC" passed to the build, e.g.: BUILDLINK_ENV+= CC="/usr/pkg/pthread/bin/pgcc"
2002-10-09Following up on previous, EXPR=/bin/expr on Darwin.schmonz1-2/+2
2002-10-08Note this this file is not for use by package Makefiles.jlam1-1/+4
2002-10-08Unused.jlam1-53/+0
2002-10-08Unused.jlam1-28/+0
2002-10-08Unused.jlam1-159/+0
2002-10-08Recognize ${FIND} and ${XARGS}.jlam1-1/+3
2002-10-08Substitute for ${FIND} and ${XARGS}.jlam1-1/+3
2002-10-08Recognize ROOT_USER and ROOT_GROUP in MESSAGE files.jlam1-1/+3
2002-10-08Unused! Remove it to prevent new packages from using it instead of usingjlam1-62/+0
buildlink2.
2002-10-08Fix error messages to display if the compiler tools aren't in the PATH whenjlam1-2/+2
creating the buildlink2 wrapper scripts. Based on patch in pkg/18425 by grant@netbsd.org.
2002-10-07Move BUILD_USES_GETTEXT_M4 logic to automake.mk.wiz2-6/+6
2002-10-07Document (commented) SAWFISH_THEMES variable, specifying the DISTFILES forjschauma1-1/+7
wm/sawfish-themes (default: about 180 themes available on themes.freshmeat.net)
2002-10-07Add switch GIMP_WITH_HELPBROWSER to build gimp with help browser.hubertf1-1/+7
Disables to "no", which results in no gnome-libs being needed. Patch contributed by Stefan Krüger <skrueger@europe.com> in private mail, with some changes from me.
2002-10-06Full pathname for expr command.seb1-2/+2
2002-10-06fix typo in comment and an error in the usage output (position ofdmcmahill1-3/+3
bar and libbar were swapped).
2002-10-05Mention buildlink2.txt. Closes PR 18542 by Greg Woods.wiz1-1/+4
2002-10-04Add new bsd.pkg.install.mk tunable variable: SPECIAL_PERMS.jlam2-2/+32
SPECIAL_PERMS are lists that look like: file user group mode At post-install time, file (it may be a directory) is changed to be owned by user:group with mode permissions. SPECIAL_PERMS should be used primarily to change permissions of files or directories listed in the PLIST. This may be used to make certain files set-uid or to change the ownership or a directory. Packages that install setuid executables should list them in SPECIAL_PERMS so that the correct user and group will be used for file ownership, even if the uid/gid changes between the package creation and the package installation.
2002-10-04Instead of the incredibly dense _print_* stuff, use a (hopefully) morejlam2-135/+107
readable way of print messages.
2002-10-04Add definitions for EXPR == expr, used for portable shell arithmetic. Ijlam4-4/+8
was only able to check the paths for NetBSD and Linux...Solaris and Darwin pkgsrc developers should change the path to expr in the right defs.*.mk file.
2002-10-04Don't use JAVA_HOME as the user may have it incorrectly set in thejlam1-15/+17
environment. Instead, create a new variable PKG_JAVA_HOME, which is passed to the configure and build processes via: JAVA_HOME=${PKG_JAVA_HOME} to override any environment setting for JAVA_HOME. This should fix pkg/17989.
2002-10-03Add USE_OSS to BUILD_DEFS if it's defined.jlam1-2/+6
2002-10-03Created a new variable USE_OSS that is used to enable OSS audio support injlam1-1/+8
preference to or in place of Sun audio support in various packages. People using audio/oss should set USE_OSS in their /etc/mk.conf when building packages.
2002-10-03Rename "OSS" variable to "HAVE_OSS".jlam1-8/+8
2002-10-03Sync with new autoconf213, automake14 packages and autoconf, automake updates.wiz2-13/+12
2002-10-03Back out previous -- needs more thought.jwise1-4/+4
2002-10-03Fix a long-standing problem with dependencies for java packages, introducedjwise1-4/+4
when support for BUILD_DEPEND-only java packages was introduced -- this problem was preventing java from being registered as a dependency for a number of java-based packages.
2002-10-03Invent a new publicly readable variable OSS that is YES/NO for whetherjlam1-3/+15
audio/oss is installed. Also add an example in the comments at the top of the file that shows how to use the OSS variable.
2002-10-03Create "DEVOSSSOUND" which is used where we'd like for programs that usejlam1-1/+9
the ossaudio emulation to use /dev/sound instead of /dev/audio. For OSS, DEVOSSSOUND == DEVOSSAUDIO == /dev/dsp.
2002-10-03Recognize when 4Front OSS is installed on a NetBSD system and use realjlam1-7/+13
OSS instead of the ossaudio OSS emulation library when building software.
2002-10-02add AUTORECONF variabledillo1-1/+4
2002-10-02add makefile fragments for packages that need automake / autoconf to build.dillo2-0/+61
2002-10-01Document NS_INST variable, determining if netscape7 uses the complete orjschauma1-1/+6
the recommended (default) install, as pointed out by wiz.
2002-10-01Really, really fix the problem I was trying to fix with rev 1.6. I wantjlam1-7/+29
to only add -Ldir/.libs for *.la files that are not named with absolute paths or named with an absolute path starting with ${WRKSRC}. This should fix the problem with converting kdebase3 to buildlink2.
2002-09-30Add PKG_LANG variable, defaulting to english.jschauma1-1/+9
Currently only used by www/netscape7 but this can potentially be used by many packages to help localize the installation. Ok'd by wiz.
2002-09-29Correctly fetch ALLFILES containing '=' charactersrh1-6/+6
2002-09-28* Split _BLNK_TRANSFORM_SED into 4 variables, as even with 3 it wasjlam5-23/+40
overflowing the make variable size limit. * Rename _BLNK_WRAP_ENV to _BLNK_WRAP_SETENV, and use _BLNK_WRAP_ENV to set the shell environment for the wrappee. Allow BUILDLINK_WRAPPER_ENV to add to the shell environment.
2002-09-28Nuke a bogus invocation of 'pkg_info -I' and use 'pkg_info -e' instead.uebayasi1-13/+3
Simplify the '!=' lines. Pointed out by wiz (a.k.a. wizd(8)).
2002-09-27Make machine/soundcard.h an alias for sys/soundcard.h if non-existentrh1-2/+9
2002-09-27Provide a way for buildlink2.mk files to convert a build dependency tojlam1-5/+6
a full dependency. BUILDLINK_DEPMETHOD.<pkg> is now a space-separated list of the words "full" and/or "build", and if any of them is "full", then a full dependency on <pkg> is used. buildlink2.mk files may now do: BUILDLINK_DEPMETHOD.<pkg>+= full to convert from a build to a full dependency. Previously, if a package Makefile set BUILDLINK_DEPMETHOD.<pkg>=build, there was no way to override its value consistently.
2002-09-27Add MASTER_SITE_GNUSTEPrh1-1/+10
2002-09-27Add share/locale/is.wiz4-4/+20
2002-09-27Create a new variable USE_X11_LINKS that controls whether packages thatjlam2-3/+29
use buildlink2 and set USE_X11 will use x11-links, or if they will simply symlink the X11 files directly into ${BUILDLINK_DIR}. If USE_X11_LINKS is "YES" (the default), then x11-links is used. If USE_X11_LINKS is "NO", then the X11 files are symlinked directly. There is a choice here between speed and flexibility. Using x11-links is faster since you don't need to spend time symlinking all of the X11 files into ${BUILDLINK_DIR}. However, if you update your X11 installation, then the x11-links package will likely be out-of-date. Conversely, directly symlinking the X11 files will protect you from changes in your X11 installation when you update, but there is a (small) time penalty to have to do it for every package that uses X11.
2002-09-27Change /usr/lib/*.la to ${BUILDLINK_DIR}/lib/*.la in libtool archives whenjlam1-1/+2
buildlinking them into ${BUILDLINK_DIR}. This should allow cases where a /usr/lib/libintl.la escaped into an installed libtool archive (during the time when buildlink2 was broken for about 4 days) to be handled properly.
2002-09-26When PKG_DEBUG_LEVEL=2, set_PKG_DEBUG_SCRIPT is set to "${SH} -x". Usejlam2-6/+12
_PKG_DEBUG_SCRIPT when running the INSTALL/DEINSTALL scripts so that they may be easier to debug.
2002-09-26Create DEVOSSAUDIO, for the default OSS audio device.jlam1-4/+14
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-13 16:49:19 +0000