Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
I should mention Arrigo Triulzi, who provided a login to an OpenBSD 3.0
machine and also a machine to play with OpenBSD 3.2 and pkgsrc. Thanks
Arrigo!
|
|
|
|
|
|
patching Makefile not Makefile.in. Depends on HAS_CONFIGURE || GNU_CONFIGURE.
|
|
|
|
The logic is:
- if package defines USE_PKGLOCALEDIR and PKGLOCALEDIR is not 'share' as GNU
autotools expects then
- fix variables 'localedir', 'gnulocaledir' and define coorect 'LOCALEDIR' in
the Makefile.in.* files
From Packages.txt:
10.29 Packages providing locale catalogues
==========================================
If the package provides its own locale catalogues, the variable
USE_PKGLOCALEDIR should be defined. It will ensure that the package's
Makefile template files are fixed and point to the correct locale directories
(which may vary, depending on OS), if necessary. See also section 5.1 for
details about ${PKGLOCALEDIR}. This functionality is buildlink2-only.
|
|
* Set CONFLICTS appropriately so that Emacs version and XEmacs version of a
package can't be installed at once.
|
|
the case where X11BASE is a subdirectory of LOCALBASE, e.g. /usr/pkg/X11R6.
|
|
|
|
We do not have opsys-specific patches, and this note becomes more
and more confusing the more OSs we support with pkgsrc.
Pointed out and patch provided by Jeremy C. Reed (reed at reedmedia dot net)
in PR pkg/19172.
|
|
Move SAWFISH_THEMES to proper location.
|
|
USE_BUILDLINK2 is defined. AUTOMAKE_OVERRIDE == "yes" is the default, and
means that pkgsrc will try to avoid executing the GNU autotools during the
build process. Setting AUTOMAKE_OVERRIDE to "no" will avoid these extra
steps by pkgsrc, so that the GNU autotools will be automatically invoked
if they are found (though they may not necessarily invoke the correct ones
and the effects may be surprising...do this only if you know what you are
doing).
|
|
|
|
Addresses PR 19159 by grant@netbsd.org.
|
|
generate the "sed-substituted" file with a ".blsav" suffix. This is
primarily useful for debugging purposes.
|
|
|
|
update.
|
|
Note we vary only be a couple of lines for sh5le.
|
|
interface
|
|
could not correctly de-install packages if cwd is part of PLIST of the
to be deleted package. This closes PR pkg/18384.
|
|
being run during the first part of a make; make install sequence.
(As suggested by Greg A. Woods on tech-pkg.)
|
|
because I'm a slacker. Take a months-old hint from Johnny in PR
16628 and set PKG_CREATE_USERGROUP to NO in the meantime.
|
|
Addresses PR pkg/18077 and PR pkg/18430 and possibly others.
|
|
that are outside of ${LOCALBASE} belong to the package that lists them.
If the directory already exists before the package is installed, then
we don't presume ownership of the directory.
This addresses pkg/18383 by Grant Beattie.
|
|
into whether USE_BUILDLINK is "no".
|
|
|
|
|
|
Also document what that section of the Makefile does.
|
|
|
|
+ umount filesystems in the reverse order from that which they were mounted
+ null-mount /lib and /libexec in a way more consistent with the original
|
|
the GNU auto* tools from being executed during the build process. We now
just create shell scripts that simply return an error status for each of
the GNU auto* tools in ${BUILDLINK_DIR}/bin and ignore the other goop in
bsd.pkg.mk that tried to accomplish the same thing.
|
|
|
|
Use 'if cmd1; then :; cmd2; fi' instead of 'if ! cmd1; then cmd2; fi'
|
|
|
|
Tested on FreeBSD 4.7-RELEASE/i386.
|
|
|
|
shells to /etc/shells.
This feature can be disabled by setting PKG_REGISTER_SHELLS to NO in
/etc/mk.conf.
An excerpt from Packages.txt, section 10.28:
10.28 Packages providing login shells
=====================================
If the purpose of the package is to provide a login shell, the variable
PKG_SHELL should contain the full pathname of the shell executable installed
by this package. The package Makefile also must include
"../../mk/bsd.pkg.install.mk" prior to the inclusion of bsd.pkg.mk to use the
automatically generated INSTALL/DEINSTALL scripts.
An example taken from shells/zsh:
PKG_SHELL= ${PREFIX}/bin/zsh
.include "../../mk/bsd.pkg.install.mk"
The shell is registered into /etc/shells file automatically in the
post-install target by the INSTALL script generated by bsd.pkg.install.mk and
removed in the deinstall target by the DEINSTALL script.
|
|
|
|
back to the current page, just list it as regular text.
- Put each dependency hyperlink on a separate line in the README.html file.
These were both noted by Thomas Klausner in a private email.
|
|
|
|
correctly with Solaris' ksh (not sure why this didn't break on NetBSD's
/bin/sh). Analysis and fix by Jonathan Perkin <sketch@rd.bbc.co.uk>.
|
|
This is to override the default CC=cc, CXX=c++, LD=ld, etc. settings in
CONFIGURE_ENV and MAKE_ENV, e.g.:
BUILDLINK_SETENV.CC= CC=gcc
|
|
libtool to install libraries or programs.
|
|
avoid simply appending to it.
- add some additional error checks when using the -r/--restart options to
make sure that the database exists and give a useful error message if it
doesn't
|
|
can just test whether X11BASE is /usr/openwin (see x11.buildlink2.mk).
|
|
based on the value of OPSYS. This was breaking pkgsrc on Solaris.
|
|
directory of a single package (e.g. graphics/gimp) for which a README.html
is to be generated. This provides the required hook to be able to use this
script to generate a README.html file for a single package as well as
for all packages.
|
|
|