summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2006-03-22Remove an unsed script -- print-la-libnames was replaced withjlam1-77/+0
plist/libtool-expand after the plist module was committed.
2006-03-21Add the pa_IN locale directory, initially used by the iso-codes 0.50jmmv13-13/+65
package (coming after the freeze).
2006-03-20Strip trailing whitespace.jlam1-2/+2
2006-03-20postgresql81 has moved from wip to pkgsrc.uebayasi1-2/+2
2006-03-20Create a new variable EMACS_MODULES that is a list of "standard" elispjlam1-15/+35
modules that is required by the package. The allowed modules are "base" and "leim". EMACS_USE_LEIM is deprecated and should be replaced with EMACS_MODULES+=leim.
2006-03-20* Creates a new variable PKGINFODIR (named similarly to PKGMANDIR)jlam8-66/+109
that is a purely user-settable variable to represent the relative path under ${PREFIX} where info files are stored and "dir" files are managed. PKGINFODIR defaults to "info". INFO_DIR still works, but will be obsoleted after the 2006Q1 branch. * Modify GNU_CONFIGURE_INFODIR to only honor ${PKGINFODIR} if the package installs directly into ${PREFIX} and not some subdirectory under ${PREFIX}. This fixes packages that don't really honor $(infodir) all that well, and also avoids PLIST problems relating to directory removal for those packages. * Since the majority of Emacs Lisp packages use GNU_CONFIGURE, just set GNU_CONFIGURE_INFODIR directly to ${EMACS_INFOPREFIX}, which is the Emacs-distro-specific location for info files. Also pass EMACS_INFOPREFIX through PLIST_SUBST for PLIST substitution. * INFO_FILES should be defined if the package installs info files. If the info files are not listed in the PLIST, then INFO_FILES must list the filenames for the info files installed by the package, which are assumed to be located in ${PREFIX}/${PKGINFODIR}. * The plist module can now better detect info files listed in PLISTs and exports a command to the pkginstall module to append info file names to the +INFO_FILES scriptlet at install-time. * The print-PLIST target is updated to properly list info files in the auto-generated PLIST. * The check-files code is updated to skip all "dir" Info database files.
2006-03-19Modify the INSTALL script to allow for selective unpacking of a scriptlet.jlam9-26/+31
2006-03-19Teach the tools framework about "texi2html".jlam1-1/+12
2006-03-19ftp.fi.muni.cz mirrors GNU, CPAN and CTAN, add it to the appropriatejdolecek1-4/+7
MASTER_SITE_* lists as a courtesy for Czech users
2006-03-18Remove leftover code sections guarded by _USE_PLIST_MODULE which wasjlam13-117/+13
mainlined long ago.
2006-03-17Ensure that we invoke a brand new make when creating the INSTALL/DEINSTALLjlam1-5/+6
and rc.d scripts so that we source the latest makevars.mk file and get the latest set of cached variables. This fixes problems where BUILDLINK_PREFIX.* wasn't being expanded correctly when substituting into an INSTALL script.
2006-03-17Allow INSTALLATION_DIRS to contain absolute paths so long as they beingjlam1-2/+6
with ${PREFIX}. This simplifies re-using variables that contain full paths.
2006-03-16Teach the tools framework about "makedepend", supplied by the imakejlam1-2/+2
packages.
2006-03-15Always run the pkginstall framework targets to generate thejlam2-20/+44
INSTALL/DEINSTALL and rc.d scripts, regardless of whether NO_BUILD is defined or not. We do this by renaming the main "build" target to "_build", and creating a new "build" target that has "_build" and "pkginstall" as dependencies. This allows the "build" and "install" targets to be consecutive, so no changes in behavior are visible to the user. Because the pkginstall targets are no longer run within the protection of the locks during the build phase, we need to manage locking within a new "pkginstall" target.
2006-03-15Back out previous... it was part of some larger changes that were neverjlam1-2/+3
committed and I got ahead of myself.
2006-03-15Rototill of how the various template parts of the INSTALL and DEINSTALLjlam14-261/+283
scripts are generated. The various scriptlets in pkgsrc/mk/install are now full templates that can be combined to form the INSTALL and DEINSTALL scripts. All of the templates have either leading or trailing blank lines so that when they are concatentated, the full INSTALL and DEINSTALL scripts will still be easy to read. All of the generated template sources for the INSTALL and DEINSTALL scripts are now stored in ${WRKDIR}/.pkginstall for local consistency and have been renamed so that they are not dot-files. The "data" for the +* scriptlets are now generated in a separate step and instead of being appended to the unpacked scriptlet are now appended to the INSTALL script itself. When the scriptlets are unpacked, the corresponding data lines for each scriptlet are pulled out of the INSTALL script and put into the unpacked scriptlets. This makes it easy to append more data lines during the install phase without needing to regenerate the INSTALL script.
2006-03-14Properly rename "info" to ${INFO_DIR} in any @dirrm statements. Alsojlam1-6/+12
add a guard so that we don't re-expand any "info" in ${INFO_DIR} again.
2006-03-14We can always pass --infodir to configure scripts, regardless of whetherjlam1-3/+2
or not there are info files to be installed.
2006-03-14Teach the plist framework a new variable IGNORE_INFO_DIRS that is ajlam2-7/+30
list of ${PREFIX}-relative paths of directories that do *not* contain info files. This allows avoiding the auto info-file-entry munging that occurs for all PLIST entries that are in directories named "info".
2006-03-14Sort _PLIST_AWK_ENV.jlam1-2/+2
2006-03-14Restructure pattern-actions a bit so that we're not lumping everythingjlam1-8/+20
into the last action. This makes it easier to understand the flow.
2006-03-14Sync variable names in comments with recent changes to install framework.tron2-4/+4
2006-03-14Modify the pkginstall framework so that it manages all aspects ofjlam3-134/+125
INSTALL/DEINSTALL script creation within pkgsrc. If an INSTALL or DEINSTALL script is found in the package directory, it is automatically used as a template for the pkginstall-generated scripts. If instead, they should be used simply as the full scripts, then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC explicitly, e.g.: INSTALL_SRC= ${PKGDIR}/INSTALL DEINSTALL_SRC= # emtpy As part of the restructuring of the pkginstall framework internals, we now *always* generate temporary INSTALL or DEINSTALL scripts. By comparing these temporary scripts with minimal INSTALL/DEINSTALL scripts formed from only the base templates, we determine whether or not the INSTALL/DEINSTALL scripts are actually needed by the package (see the generate-install-scripts target in bsd.pkginstall.mk). In addition, more variables in the framework have been made private. The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are more sensible names given the very few exported variables in this framework. The only public variables relating to the templates are: INSTALL_SRC INSTALL_TEMPLATE DEINSTALL_SRC DEINSTALL_TEMPLATE HEADER_TEMPLATE The packages in pkgsrc have been modified to reflect the changes in the pkginstall framework.
2006-03-13Replaced option "spamassassin-test-net" by generic option "online-tests".heinz1-2/+2
Adapted the single quotation marks in option spamassassin-test-prefork to the commonly used double quotation marks.
2006-03-13Makefiles that include oss.buildlink3.mk can now check the value ofjlam1-2/+25
OSS_TYPE to determine whether or not a native OSS implementation is present or not. OSS_TYPE just exports the value of IS_BUILIN.oss, but exports it early enough where it can be used within a package Makefile, e.g.: .include "../../mk/oss.buildlink3.mk" .if ${OSS_TYPE} == "none" CONFIGURE_ARGS+= --without-oss .endif This should fix builds of some packages that include "oss.buildlink3.mk" on platforms where there is no OSS in the base system, e.g. Mac OS X and Solaris.
2006-03-12Added the variable PHASE_MSG, STEP_MSG, WARNING_MSG and ERROR_MSG torillig1-1/+5
facilitate the generation of consistent-looking progress messages.
2006-03-11+zsh-multibyteuebayasi1-0/+1
2006-03-11Export EMACS_VERSION_MAJOR and EMACS_VERSION_MINOR to packages using emacs.mk.uebayasi1-1/+15
2006-03-11BUILD_DEPENDS on gettext-tools not gettext for BUILD_USES_MSGFMT.reed1-2/+2
2006-03-10Cosmetic change: reorder some lines locally to make it easier for mejlam1-13/+13
to understand.
2006-03-10Expose fewer knobs for a user to tweak by making more variables private.jlam1-57/+53
2006-03-10Correct the path to the bsd.prefs.mk file and move it to the properjlam1-2/+3
location in a buildlink3.mk file.
2006-03-10Don't define DEINSTALL_FILE or INSTALL_FILE if the corresponding *_SRCjlam1-1/+5
variables are empty.
2006-03-10replace-interpreter should use REPLACE_FILES.${lang} instead oftonio1-3/+3
_REPLACE_FILES.${lang}
2006-03-10Include bsd.prefs.mk before testing ${OPSYS}.wiz1-1/+2
2006-03-09Make it safe to include bsd.pkginstall.mk directly in bsd.pkg.mk, andjlam3-110/+103
drop pkginstall.mk, which did the same thing. Also, rework some of the targets so that we avoid needing to inspect *_MEMBERS variables within make -- we defer the check to the shell code invoked by the targets. All changes are internal and don't affect existing packages in a visible way.
2006-03-09Replace references to ossaudio.buildlink3.mk with oss.buildlink3.mk.jlam1-6/+0
Remove deprecated ossaudio.buildlink3.mk.
2006-03-09mention SUSE_PREFER=10.0 in coments (but keep 9.1 as default)tonio1-3/+4
2006-03-09Reimplement OSS audio handling in pkgsrc. Add two new files:jlam3-79/+133
oss.buildlink3.mk oss.builtin.mk that work like modern buildlink3.mk and builtin.mk files do. We no longer support audio/oss (which will be removed shortly). Mark ossaudio.buildlink3.mk for deprecation after all references to it have been replaced with "oss.buildlink3.mk" in package Makefiles.
2006-03-09Check that INFO_FILES is defined before using its value. Fixes PR pkg/33043.jlam1-2/+2
2006-03-09Since the REPLACE_INTERPRETER is used in more and more packages, it isrillig1-4/+14
not good style to make the package author define variables from the pkgsrc-internal namespace. The variables REPLACE.* and REPLACE_FILES.* can now be used as replacements for _REPLACE.* and _REPLACE_FILES.*. Support for the old variable names will be removed after 2006Q2.
2006-03-09Reimplement the info-file handling so that we use an +INFO_FILESjlam9-82/+176
scriptlet to manage the info-file registration. The new scriptlet's template is install/info-files. Remove obsolete texinfo.mk and install/install-info. No changes to package Makefiles are necessary -- the re-implementation is internal to pkgsrc infrastructure.
2006-03-08Teach the tools framework about Darwin's tclsh and wish.minskim1-1/+3
2006-03-08Set LOWER_OPSYS_VERSUFFIX on Darwin.minskim1-1/+2
2006-03-07For the user or group removal message, don't set they can be removedreed1-3/+3
if no other packages are using them, but if no other "software" is using them. Just in case, they are using a user and/or group without a package using it.
2006-03-06Teach the tools framework how to supply a pkgsrc version of install-infojlam11-38/+56
if a native one isn't available. We ensure that the "install-info" tool in the tools directory is a no-op since the real info file registration is handled by the INSTALL/DEINSTALL script in pkgsrc/mk/pkginstall/install-info.
2006-03-05It's probably "/bin/makeinfo", not "/usr/bin/makeinfo".jlam1-3/+3
2006-03-05* Teach the tools framework how to supply the pkgsrc version ofjlam12-100/+79
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD when determining whether the native makeinfo can be used. * Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo. * Get rid of all the "split" argument deduction for makeinfo since the PLIST module already handles varying numbers of split info files correctly. NOTE: Platforms that have "makeinfo" in the base system should check that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are correct.
2006-03-04Handle info directory trees that aren't rooted directly in ${PREFIX}, e.g.jlam1-4/+8
${PREFIX}/<pkg>/info, etc.
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.