summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2005-02-07Instantly deprecate USE_PAM from pkgsrc as its value is being set fromjlam1-4/+1
within NetBSD-current's bsd.own.mk, which conflicts with its usage in pkgsrc. The package that use USE_PAM have been converted to use the bsd.options.mk framework. This should fix PR pkg/29257.
2005-02-07The lists of ghostscript version patterns should match all ghostscriptjlam1-9/+7
versions (minus any PKGREVISIONs) less than or equal to the latest version of each ghostscript available in pkgsrc (minus any PKGREVISIONs). For example, if the print/ghostscript-esp is at 7.10, then the list of patterns for ghostscript-esp should match all versions <=7.10, which is [0-6].* 7.[0-9]* 7.10
2005-02-07pg80 is now in databases, not wipdan1-2/+2
2005-02-07don't recognise pg80 as pg74 alsodan1-2/+2
2005-02-05Set PKG_REFCOUNT_DBDIR in the environment for the +INSTALL script, justjlam1-1/+4
like pkg_add(1) does in pkg_install-20050204.
2005-02-04Add tl locale, initially used by glib 2.6.2.jmmv13-13/+65
2005-02-04Bump PKGTOOLS_REQD to 20050204. This version of pkg_install passesjlam2-4/+3
the correct information to the +INSTALL and +DEINSTALL scripts to fix problems with binary packages incorrectly locating the reference counts database, e.g. /var/db.refcount.
2005-02-03Create a new INSTALL script action "UNPACK" that unpacks all of thejlam1-6/+6
sub-scripts.
2005-02-02Next round of install script cleanup -- we now create +FILES,jlam6-349/+533
+RCD_SCRIPTS, and +PERMS subscripts to handle copying config files and rc.d scripts, and setting special permissions on files. The +FILES and +RCD_SCRIPTS are basically identical except for different embedded packets of data, and they feature reference-counting for the files in case multiple packages share the same config file. Garbage-collect unused functions and definitions in the install scripts now that the subscripts are self-contained.
2005-02-01allow postgresql80 (from wip), similar to java-vm.mk and jdk14abs1-3/+8
2005-01-31In the usage message, note that the CHECK-* actions can take an optionaljlam2-4/+4
metadatadir argument.
2005-01-31Note in the usage that CHECK-* take an optional metadatadir argument.jlam1-2/+2
2005-01-31Add missing "fi".jlam1-1/+2
2005-01-31Fix automatically adding users and groups after the {GROUP,USER}ADDjlam2-11/+13
definitions were removed from mk/install/headers. The checks for whether {GROUP,USER}ADD are defined are now moved to the usergroup script.
2005-01-31Add RCS Id.jlam2-0/+4
2005-01-30Convert the Java related packages to use the alternatives system. To dojmmv1-1/+8
this, we only need some simple logic in java-env.mk to automatically generate an ALTERNATIVES file for us. There are two exceptions, though: fastjar and jikes (pointed out by tv@), which do not use this file; they have to be handled manually. Bump PKGREVISION for all affected packages. While doing this, remove the java-wrapper package, obsoleted by the new functionality provided by pkg_alternatives.
2005-01-28Don't make pkgsrc depend on dc(1) to be present in the system. Sincejlam14-36/+18
we already use awk so pervasively in pkgsrc, simply use awk in place of dc for simple computations.
2005-01-28Avoid hardcoding the refcount database into the INSTALL scripts. Wejlam3-13/+6
now simply make ${PKG_REFCOUNT_DBDIR} always be ${PKG_DBDIR}.refcount so that it always follows the location of ${PKG_DBDIR}. This preserves the ability for PKG_DBDIR (and PKG_REFCOUNT_DBDIR) to be different on different machines despite using the same binary packages.
2005-01-28Move the default directory for the reference counts database outsidejlam1-4/+5
of ${PKG_DBDIR} to avoid problems with the package tools thinking that it is a bad package. The default directory is ${PKG_DBDIR} with ".refcount" appended to the name. This may be set explicitly through PKG_REFCOUNT_DBDIR in /etc/mk.conf (bootstrap users may want to do this, although the default value should do the right thing).
2005-01-28Remove entries for GROUPADD and USERADD from header since they're alljlam1-3/+1
handled within the usergroup script.
2005-01-28Pretty-print the users and groups that may need to be removed duringjlam1-24/+41
CHECK-REMOVE. The users and groups are now printed on the same line with whitespace separating the entries (for easy copy-and-pasting info commands), and wrapping to successive lines if we overflow the length of the current line.
2005-01-28If PKG_SYSCONFSUBDIR is non-empty, then add ${PKG_SYSCONFDIR} to thejlam1-2/+2
list of +DIRS-maintained directories. This allows for a package to specify where its config files should go and creates the directory automatically, even if it doesn't have any example config files to put in place.
2005-01-28Note the end of the install-dirs unpack template within the INSTALLjlam1-1/+3
script.
2005-01-28Continue with install script cleanup -- we now create a +USERGROUPjlam5-153/+419
script that is unpacked by the +INSTALL script at PRE-INSTALL time before any other actions take place, and invoke +USERGROUP to create any necessary users and groups. Remove the now-unused code for PKG_USERS and PKG_GROUPS from the install and deinstall templates. We also reference count the users and groups and store the reference counts in ${PKG_DBDIR}/.refcount/{users,groups}. This allows multiple packages to register that they use same users and groups, and allows +USERGROUP to be invoked at any time to repair an installed package. Also fix the install and deinstall templates to invoke the CHECK-* actions with ${PKG_METADATA_DIR} so that the correct PKGNAME can be derived. This fixes the weird messages asking the user to create directories for ".pkgdb" during a "make install".
2005-01-28Use reference counts to properly account for the creation and removaljlam5-197/+282
of directories needed for the proper functioning of each package. The +INSTALL script unpacks a +DIRS script that adds and removes directories. The +DIRS script entirely encapsulates the directory creation and removal, and completely replaces the code in the mk/install/install and mk/install/deinstall templates that handled {MAKE,OWN}_DIRS and {MAKE,OWN}_DIRS_PERMS. The +DIRS script is meant to be executed from within the package meta-data directory, e.g. /var/db/pkg/<pkgname>. It's usage is: ./+DIRS ADD|REMOVE|CHECK-ADD|CHECK-REMOVE The ADD and REMOVE actions cause the necessary directories to be added or removed from the system. The CHECK-ADD and CHECK-REMOVE actions print out informative messages prompting the user to either create or remove some necessary directories. The behaviour of "ADD" is such that if the directory already exists on the system and is not already ref-counted, then that directory is marked as "pre-existing". On "REMOVE", pre-existing directories are left untouched on the filesystem. At any time, the root user can sanity-check the directories needed by packages by invoking all of the +DIRS scripts with the "CHECK-ADD" action. If there are missing directories, then invoking all of the +DIRS scripts with the "ADD" action will ensure that any missing directories are created. The reference counts database is stored in ${PKG_DBDIR}/.refcount. The reference counts related to directories managed by the +DIRS script are stored in ${PKG_DBDIR}/.refcount/dirs. If the directory reference counts database is removed, then invoking all of the +DIRS scripts with the "ADD" action will reconstruct the database; however, directories may be marked as being pre-existing, so they won't be removed at package de-installation (although a message will be displayed informing the user that those directories can be removed).
2005-01-27Move the creation of ${PKG_DB_TMPDIR} to when we create ${WRKDIR}.jlam1-2/+3
This ensures that it's always created with the same user/group/mode as ${WRKDIR}, so if a non-root user thinks he has permissions to remove ${WRKDIR}, then that expectation will remain true for ${PKG_DB_TMPDIR}.
2005-01-27Pass the correct programs to the mkdatabase script.sketch1-2/+2
2005-01-27Fix handling of PREPEND_PATH in dependency-recursed builds.tv1-1/+3
2005-01-27Cleanup: wrapper-defs.mk is no longer optional; remove its conditional.tv1-5/+4
(...and if it were optional, it should have been an .sinclude anyway.) Sanity: If mk/platform/${OPSYS}.mk is missing, don't assume NetBSD is it. pkgsrc now depends on a valid platform file for an OS, so require it. (Still includes NetBSD.mk, but sets PKG_FAIL_REASON.)
2005-01-27Move the PREPEND_PATH for LOCALBASE/bin (and optionally X11BASE/bin) to atv2-9/+9
spot that will come before compiler.mk (in bsd.prefs.mk). Previously, LOCALBASE/bin was appearing earlier in the path than work/.<compiler>/bin, which could cause the Wrong Thing to happen.
2005-01-26Also substitute for PWD_CMD so we can use it in the INSTALL scripts.jlam1-1/+2
2005-01-26Create a new variable "INSTALL_UNPACK_TMPL" that points to a list ofjlam1-1/+3
shell script fragments that unpack sub-scripts before the any of the other PRE-INSTALL stages are run.
2005-01-26Fix so that we preserve /usr/lib/foo.so on the command line.jlam1-16/+28
2005-01-25Set argmatch=yes when we transform /some/where/libfoo.so intocube1-1/+4
-L/some/where -lfoo so that the arguments we push on the stack are actually used in logic. Should solve the issue build bash with option 'static' enabled reported on netbsd-users. OK'd by jlam@.
2005-01-25Relax need to put GNU_CONFIGURE before inclusion of bsd.prefs.mk:tv13-49/+27
Convert _OPSYS_MAX_CMDLEN to a plain _OPSYS_MAX_CMDLEN_CMD variable, which is not evaluated by a shell until CONFIGURE_ENV is expanded (and only then if USE_LIBTOOL+GNU_CONFIGURE are both set).
2005-01-25Explicitly use -g to avoid relying on default behavior.jmmv1-3/+3
2005-01-25Redo previous per suggestion from reed@. Do not process the alternativesjmmv1-21/+10
until the pkg_alternatives package has been manually installed. This way we drop the dependency on that package.
2005-01-25Make the usage of alternatives optional through the PKG_ALTERNATIVES variable,jmmv1-6/+19
which is similar to PKG_CONFIG. This does not change how the binary packages are built, only whether the pkg_alternatives command should be run at package installation/deinstallation time or not. The variable can take either YES or NO as values and defaults to YES.
2005-01-25Add alternatives.mk, a file used to manipulate the alternatives system.jmmv2-1/+61
A package can optionally provide an ALTERNATIVES file which contains pairs of wrapper/alternative, one per line. The file is then used by the install and deinstall scripts to register the alternatives and to create the appropriate wrappers. Make bsd.pkg.mk include this new file. This happens unconditionally to keep all the alternatives logic in an independent file. Otherwise, some of the stuff could have to be moved to bsd.pkg.mk, breaking consistency.
2005-01-25only try to run the build if "cd /usr/pkgsrc" is successful.grant1-2/+2
2005-01-24Add python22, python24 to base addresses list.tv1-1/+3
2005-01-24Disallow -rdynamic (was being attempted by shells/scsh).tv1-2/+2
2005-01-24Merge a little visual-only cleanup from the tv-derecurse branch:tv1-103/+71
Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24Merge down deferred PREPEND_PATH handling from the tv-derecurse branch.tv2-45/+37
Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24Make CHECK_FILES_SKIP_CMD into a single grep, using a ${var:@foo@bar@} loop.tv1-7/+2
2005-01-24Merge down deferred EVAL_PREFIX handling from tv-derecurse branch.tv4-25/+16
Also move its definition later in bsd.pkg.mk, so that it actually works for compiler/*.mk (which is why those files originally had to provide "defaults" for their variables -- they never did get evaluated).
2005-01-24Merge down janitorial change from tv-derecurse branch:tv2-5/+7
Move definition of PKGSRC_COMPILER to defaults/mk.conf, to make it more readily seen by the user.
2005-01-24Merge down janitorial change from tv-derecurse branch:tv1-9/+5
No need to do .som_done dance; just show the message as part of the pre-extract phase. If that means showing it more than once if the extract is interrupted and restarted, no harm done.
2005-01-24Per default, only create md5 and sha1 checksums.jschauma2-17/+25
(These are available on all platforms via digest(1).) Set commands for other checksums on a per OPSYS basis. Set MKSUSM=yes back as the default.
2005-01-24Not all OS's have all the checksum tools available to make MKSUMS=yes work.tv1-2/+2
Default it to "no" instead.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-27 02:57:06 +0000