| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
needs that).
|
|
Noted by Will Andrews <will@physics.purdue.edu> in private mail.
|
|
directly adding a dependency on f2c.
|
|
|
|
EVAL_PREFIX= FOODIR=foo
is defined, then FOODIR's value is only saved if the package foo was
found. This causes FOODIR to keep being reset until the package foo
is installed, which makes EVAL_PREFIX work properly with buildlink.mk
files. This should fix various problems people have been having with
files not being linked in when a dependency is built via a "make build"
in a package that uses that dependency further up the chain.
|
|
|
|
|
|
document it in mk.conf.example. Adresses pkg/13343.
|
|
to aid in debugging problems.
|
|
even has a file system called /usr or that thats the right one.
|
|
to remove it, then try again with 'pkg_delete -r'. This can happen when
some other out date pacakges are installed and we're trying to bulk build
a single package.
|
|
dependencies on the package are added through buildlink. Also show how
to use EVAL_PREFIX to set BUILDLINK_PREFIX.foo.
|
|
.if .if
.if . if
.else => . else
.endif . endif
.endif .endif
Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of
merging latest changes with the OpenPackages project. Thanks Marc!
|
|
|
|
makefiles, and this interferes with the conditional definition of FILE
in defs.*.mk.
|
|
${BUILDLINK_DIR} in Linuxish locations.
|
|
exist, then spit out a big warning to stderr (since we often capture stdout
for other purposes) and don't try and descend to that directory.
|
|
- The "sun-jre" and "sun-jdk" packages can now be directly selected by
setting "PKG_JVM" to "sun-jdk". "JAVA_HOME" is set to
"${LOCALBASE}/java/jre/bin" in this case which fixes PR pkg/11901
by myself.
- Only set "CLASSPATH" to "${JAVA_HOME}/lib/classes.zip" if that file
really exists.
|
|
|
|
with "grep" through it in Mesa library handling.
|
|
under Solaris/SPARC. Default is "sparcv7".
|
|
- Add missing "${_PKG_SILENT}${_PKG_DEBUG}" in front.
- Create category directories as required.
|
|
installed package with the "pkg_tarup" utility.
|
|
redefined later.
|
|
to install things like "open.3" and "lib.3" which confuse users. Perl
ships with a documentation tool, "perldoc", for this purpose; create a
MESSAGE indicating that it should be used instead. (Perl still installs
command line program manual pages in man1.)
* Integrate bsd.perl.mk into the perl5-base build where it should have been
from the beginning. The separate perl-mk pkg makes binary packages of
perl-mk completely useless[*]. Older perl builders will not break, since
<bsd.pkg.mk> contains fallback definitions that are evaluated at pkg
build time.
=====
[*] bsd.perl.mk is tightly bound to the version of perl that is installed.
The version name "perl-mk-1.1" is completely useless as a binary pkg,
since keeping multiple binary versions of perl on a FTP server means
that one of the perl-mk's will get clobbered.
However, putting the current pkgsrc PERL5_DIST_VERS in the perl-mk pkg
is also a problem, because that doesn't necessarily reflect the
installed version of perl. Snarfing the installed version at perl-mk
build time would be even uglier, since you could not then walk the tree
without perl being installed.
The cleanest solution is to integrate bsd.perl.mk into the perl5-base
pkg, and let those who have not upgraded perl yet use the runtime
definitions in <bsd.pkg.mk>.
|
|
|
|
|
|
directory too.
|
|
them in the right place. For example, a collection of binary packages can
now put uploaded with most going to the major.minor directory and the
OSVERSION_SPECIFIC ones going to the major.minor.patch directory.
still todo: the destination settings should probably be moved out of
build.conf so the same build.conf can be used by multiple machines of
different MACHINE_ARCH's at the same time. Perhaps these should be
a command line option to 'upload' instead.
|
|
package. This way we can look at a binary package and determine what versions
of the OS it may run on.
|
|
"grep" in it to avoid problems under Solaris.
|
|
|
|
|
|
of X11.rules settings below the inclusion of <X11.rules>. This should
cause overrides to work correct for XFree-3.3.x systems.
|
|
|
|
addition of the xmkmf script from the XFree86-4.0.x distribution, which
understands passing -D options through to imake. Update the dependency
on buildlink-x11 in bsd.pkg.mk for packages using USE_BUILDLINK_ONLY to
>=0.5. Also, if USE_BUILDLINK_X11 is set, then refer to ${BUILDLINK_DIR}
for location of X headers and libraries.
|
|
|
|
on macppc compiling packages.
XXX This should come from bsd.own.mk but doesn't. Why?
|
|
undefined and pass it through MAKE_ENV.
|
|
on buildlink-x11 if USE_BUILDLINK_ONLY is defined. Pass all of
CPPFLAGS/CFLAGS/CXXFLAGS/LDFLAGS to buildlink-x11 through PKGSRC_* versions
of those values. Also add preliminary support for USE_BUILDLINK_X11 for
buildlinking X11R6 instead of USE_X11 (hi zuntum!).
|
|
|
|
|
|
into one target: replace-buildlink. Get rid of BUILDLINK_FIX_LIBTOOL_SED
as it can be handled with REPLACE_BUILDLINK_SED.
|
|
package buildlink.mk file. Also change
BUILDLINK_CONFIG_WRAPPER_SED.<pkgname> to BUILDLINK_CONFIG_WRAPPER_SED.
|
|
BuildLink is defined. Bump xpkgwedge version number to 1.4 and increase
xpkgwedge dependency version in bsd.pkg.mk.
|
|
the latest libtool in its sources (there's no ltconfig, only ltmain.sh).
|
|
properly for imake-using packages, and cause pass -DBuildLink to xmkmf
(and thus to imake) if USE_BUILDLINK_ONLY is defined.
|
|
automatically.
|
|
to the sed expression used in the generated config script wrappers.
|
|
by Jim Bernard <jbernard@mines.edu>.
|
