summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2005-01-15- Move all CHECK_FILES_SKIP definitions to a central place in bsd.pkg.mk.jmmv3-46/+44
- Move the previous block of code down in the file so that all used variables are defined (specially PKG_SYSCONFDIR). Fixes a problem noticed by kristerw@'s bulk build in comms/minicom. - Ignore diff's return code, which aborts make in NetBSD 1.6.2. Also noticed by kristerw@'s bulk build. - Use full paths to do the checks, instead of relative to ${PREFIX}. Less ambiguity. Matches should be turned into regular expressions that anchor to a whole line (tried that, but found some problems). - Turn CHECK_FILES to NO by default. As said in the previous point, there are still some problems that have to be fixed and minor improvements to be done. And I have no time to fix this ATM. Yes, this definitely needs more testing. I'm sorry for all the noise. (But hey! you should set and try this feature locally! ;-)
2005-01-15Fix endif typoadrianp1-2/+2
2005-01-15Work around an undef-in-string warning caused by unexpanded $NetBSD$tv1-4/+4
id tags. Noticed by kristerw.
2005-01-14Also skip ${INFO_DIR}/dir in the check-files functionality, as this filejmmv1-1/+6
is not controlled by any package (so it won't be part of any PLIST).
2005-01-14Automatically add any of the {CONF,SUPPORT}_FILES and {MAKE,OWN}_DIRS stuffjmmv2-13/+33
to CHECK_FILES_SKIP to avoid some false positives. These directories are created in the pre-install stage so are included in the generated file list. The files are also added to silence some problems that may arise during "make replace". Found by wiz@ in the gtk2 package.
2005-01-14"uptodate-pkgtools" is actually a dead target these days. Use "fetch" intv1-2/+2
pkgtools/pkglint to determine if pkg_install needs an update.
2005-01-14Add the check-files target: when enabled, this verifies that installedjmmv1-1/+98
packages do not install more files than expected (nor delete existing files), aside other sanity checks in PKG_SYSCONFDIR and VARBASE. This behavior is only enabled if PKG_DEVELOPER is set and CHECK_FILES is YES (the default). Should let us catch problems in other systems, as some packages install different files depending on the OS they are being built (which is different to see). Furthermore, since the sanity checks done in PKG_SYSCONFDIR and VARBASE are quite agressive, only enable them when CHECK_FILES_STRICT is YES (defaults to NO). Developers should enable this feature to detect errors, but this can't be a default yet. Otherwise, lots of packages could be marked broken in bulk builds (they really are, according to "cleanliness" rules, but most of them are non-trivial to fix).
2005-01-14Only do the config.* overrides iff GNU_CONFIGURE. (defined() check neededtv1-12/+14
to make older bmakes happy.)
2005-01-14For those packages where the maintainer field can't be determined byjmmv1-1/+4
grepping, run make to get MAINTAINER's value. I've tested this with a script that tries to "simulate" this one without problems, but I can't test it "in place".
2005-01-14Modify linux-pam and solaris-pam builtin.mk files to be more generaljlam2-12/+21
in their tests for built-in versions of the PAM implementations. The MacOS X case now collapses nicely into the linux-pam case. Allow pam.buildlink3.mk to use solaris-pam as an accepted PAM implementation.
2005-01-14We need to check that IS_BUILTIN.<pam> is "yes", not just that it's empty.jlam1-2/+3
2005-01-14Add a builtin.mk file to detect Solaris' PAM, used by pam.buildlink3.mk.jlam1-0/+19
2005-01-14Create a pam.buildlink3.mk file that is used by PAM-using packages.jlam1-0/+76
It includes the correct buildlink3.mk file from either Linux-PAM (security/PAM) or OpenPAM (security/openpam) and eventually will support solaris-pam. pam.buildlink3.mk will: * set PAMBASE to the base directory of the PAM files; * set PAM_TYPE to the PAM implementation used. There are two variables that can be used to tweak the selection of the PAM implementation: PAM_DEFAULT is a user-settable variable whose value is the default PAM implementation to use. PAM_ACCEPTED is a package-settable list of PAM implementations that may be used by the package. Modify most packages that include PAM/buildlink3.mk to include pam.buildlink3.mk instead.
2005-01-14Add $NetBSD$.tv1-0/+3
2005-01-14Add override for uncommon "config.rpath" GNU config snippet. Use platformtv3-11/+543
file to indicate that override logic should be turned on. (AFAICT, only Interix is afflicted at the moment.)
2005-01-13Put back the proper variable construct for LIBTOOL_REQD that was borken intv1-5/+3
previous. (_OPSYS_LIBTOOL_REQD is only defined on some platforms, so the :U clause provides the next best choice if that's not defined.)
2005-01-13* Clean up syntax ambiguities, e.g. (my $foo = $bar) =~ ....tv1-111/+147
* Add optional verbosity to show most commands as they are being executed. * "use strict" and "use warnings". * Slurp in the varables from build.conf and bmake in one shot (amazing startup speed boost with nfs pkgsrc); put them in a hash to make "use strict" much happier with the namespace. * Fix a bunch of undef-dereference errors evidenced by "use warnings". * Exclude PKG_DBDIR from leftovers list if it is inside LOCALBASE. * Convert some <a name="..."/> constructs to <a name="..."></a> to make non-XHTML-compliant browsers happier.
2005-01-13Add TNF copyright.seb1-1/+37
2005-01-12add my copyright/license.grant1-1/+36
2005-01-12Correct my name to what I legally use.jlam3-6/+6
2005-01-12Fix checking of up to date binary packages. The problem with DEPENDStv1-3/+3
containing constructs of the form {perl>=5.8.3nb1,perl-thread>=5.8.3nb1} is that a Bourne shell "for" interprets this as two separate items in the list, nuking the {}s. The above will never succeed and thus always cause Perl-dependent packages to be rebuilt unconditionally. Just adding more \s isn't enough -- the parsing of the depends list has to be moved out of the "for" clause. So, echo them one per line and use "read" to pull them in without allowing the shell to peek at those characters.
2005-01-12set _PATCH_CAN_BACKUP=no to avoid problems with DragonFly's native patch.recht1-2/+2
Patch by Todd Willey in PR 28947
2005-01-12Use ${AWK} instead of a bare "awk".jlam1-3/+3
2005-01-12Rearrange how LANGUAGES.<compiler> is set so that we can more flexiblyjlam4-43/+59
detect when only parts of a compiler toolchain are present, e.g. the SunPro C compiler is installed, but not the Fortran-77 compiler.
2005-01-12Put a TNF copyright on files that I authored.jlam4-4/+144
2005-01-12Whitespace.jlam2-30/+30
2005-01-12Even more whitespace.jlam1-13/+13
2005-01-12Whitespace.jlam1-3/+3
2005-01-12Prepend the CCC compiler dir to the PATH so that they're found by thejlam1-1/+6
wrapper scripts.
2005-01-12Backout part of previous commit that was unrelated.jlam2-39/+29
2005-01-12Remove explicit overrides for CC and CXX that prevented using thejlam4-43/+41
definitions supplied in /etc/mk.conf. It should now be possible to pass optimization flags directly using CC and CXX when using CCC and xlC compilers.
2005-01-12Disable win32-jdk for now. It doesn't play well with bulk builds yet.tv1-14/+14
2005-01-12Remove explicit overrides for CC and CXX that prevented using thejlam2-14/+2
definitions supplied in /etc/mk.conf. It should now be possible to pass optimization flags directly using CC and CXX when using SunPro and MIPSpro compilers.
2005-01-12Nuke USE_FORTRAN and bring the f2c handling within the mk/compilerjlam8-44/+179
framework. The list of changes include: * Modify compiler.mk so that "c" is always prepended to USE_LANGUAGES, so we no longer need to say it in package Makefiles. Packages should now append to USE_LANGUAGES instead of setting it. * Create mk/compiler/f2c.mk which implements another pseudo-compiler "f2c" that may be used with any C compiler backend, e.g. PKGSRC_COMPILER= f2c ccache gcc * Teach the various "real" compiler files, e.g., sunpro.mk, mipspro.mk, etc., to use f2c if the native Fortran compiler isn't present. Packages that use Fortran should now simply include the line: USE_LANGUAGES+= fortran in the package Makefile.
2005-01-12Add MONOTONE_GROUP and MONOTONE_USER, used by the monotone-server package.jmmv1-1/+13
2005-01-11Redo previous because it had a chance to cause serious problems, and wasjmmv1-4/+4
already demonstrated by imake failing. So, instead of fiddling with PATH's value in multiple places, rely on PREPEND_PATH to get things right. Hopefully this will DTRT. At least several local tests have worked without problems.
2005-01-11nfs-pkgsrc friendliness change:tv1-8/+13
Add a knob to relocate all the global bulk state files in one setting. BULKFILESDIR; defaults to PKGSRCDIR as before.
2005-01-11Some shells can cache * lookups, so do all the rm -f's of */*/<something>tv1-5/+4
on one line. Add a message prior to doing the leftover log cleanup, as it will take a while if pkgsrc is on nfs.
2005-01-11Really skip the transformations for imake. This shows the danger injlam1-2/+2
having variables that take a "yes" value to turn off behavior.
2005-01-11Reverse PATH order in many places: instead of appending ${LOCALBASE}/binjmmv1-4/+6
and ${X11BASE}/bin to the current PATH, _prepend_ them. This way we will pick our own binaries in favour of the system ones, in the cases where conflicts exist. Also add a PREPEND_PATH for ${LOCALBASE}/bin. This should fix several packages on non-NetBSD systems. For example, ispell-spanish under Linux comes to mind, as it was using the 'ispell' binary from /usr/bin instead of the one in /usr/pkg/bin to get its configuration information. Ideally, buildlink could handle this as it does for libraries, hidding unexpected binaries ;-) No objections in tech-pkg@ (or packages@; I don't remember the exact list where I asked).
2005-01-10rc is in /usr/pkgsrc/, even in sandboxeshubertf2-4/+4
2005-01-10_ALIASES.<wrappee> should be cumulative.jlam2-6/+6
2005-01-10Upload pkgs built in sandboxhubertf1-0/+11
(wrapper to 'upload' script, similar to do-sandbox-build).
2005-01-10Allow the creation of error handlers for shell commands in make targets.jlam1-3/+41
PKG_ERROR_CLASSES is a list of error handlers, PKG_ERROR_HANDLER.<class>, to create. The default error handler will rethrow the exit code after emitting an error message that may be specified per-class with PKG_ERROR_MSG.<class>. Create error messages for the configure and build phases that inform the user of places to go looking for why the build didn't complete.
2005-01-10Fix error in previous that turned off all transformations in alljlam1-3/+3
wrappers. "Oops". We now do transformations by default, and turn them off explicitly for wrappers that don't want them, e.g. IMAKE.
2005-01-10Sort the compiler list in the comments.jlam1-3/+3
2005-01-10Whitespace nits.jlam2-10/+10
2005-01-10Remove redundant CONFIGURE_ENV lines (they're already present in thejlam1-3/+1
shell environment passed in the do-configure target.
2005-01-10Avoid the silly optimization in the make logic and push it into thejlam2-9/+10
shell script instead. We can't avoid invoking sed at least once since we need to protect the arguments against shell expansion, but we avoid invoking sed for transformations unless there actually are transformations to perform. The code is simpler, more straightforward, and logically correct now. This fixes problems with using a non-GCC compiler with packages that haven't been converted to use buildlink3, noted in PR pkg/28896.
2005-01-09Modify krb5.buildlink3.mk so that we choose a single, well-knownjlam1-59/+19
package (heimdal) for all Kerberos 5 dependencies instead of choosing the best installed Kerberos 5 package by default. This can be overridden with the following variables: KRB5_DEFAULT is a user-settable variable whose value is the default Kerberos 5 implementation to use. KRB5_ACCEPTED is a package-settable list of Kerberos 5 implementations that may be used by the package.
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-17 12:36:29 +0000