Age | Commit message (Collapse) | Author | Files | Lines |
|
"make package", from a nudge by Greg Oster. No objections, but lots of
mail, received from pkgsrc developers, to committing this during the
stability freeze, but I'd really like this to go in pkgsrc-2004Q3.
|
|
We no longer require that LIBTOOL_LA_FILES be defined in the package
Makefile, and the libtool archives should once again be listed in the
PLIST.
* Add a new yes/no variable "LIBTOOLIZE_PLIST" to control whether to
have bsd.pkg.mk automatically expand *.la files in PLISTs into the
true library names represented by the libtool archives.
* Rename the "transform-la" script to "print-la-libnames" which more
correctly reflects its function.
Many thanks to Todd Vierling for the original implementation and for
his contructive comments on how to improve the changes in this commit.
|
|
and update the documentation.
|
|
unused by pkgsrc. Noted by soda.
|
|
there is no package using ja_JP for now.
Addresses PR 26874 by SODA Noriyuki.
|
|
will help to minimize diffs for packages between the forthcoming
pkgsrc-2004Q3 branch and the HEAD after the integration of the wrapper
script framework.
|
|
logging, backslash quoting, and two queue implementations: one entirely
in memory and one using a file.
|
|
|
|
|
|
anything useful.
make it so.
|
|
|
|
a more familiar construction. BZCAT wasn't getting defined for a
bzip2-compressed patch in my tree; now it is.
|
|
|
|
|
|
|
|
These are supported options from the soon-to-be-committed wrapper
framework and are meant to more precisely state the intended
transformation. Also just skip over unknown commands instead of
generating an error.
|
|
|
|
|
|
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
|
|
down we get the correct value for _PATCH_BACKUP_ARG and friends.
|
|
verbose message displayed on patch failure is in fact displayed on
patch failure. It defaults to "no" if PKG_DEVELOPER is defined,
"yes" otherwise. While here, rename PKG_PATCH_FAIL to PKGSRC_PATCH_FAIL.
|
|
real effect at all.
|
|
Perl in Interix ships, so it's an appropriate default for the OS. (Still
overrideable in mk.conf explicitly.)
|
|
|
|
target takes care of this case already.
|
|
|
|
For me this fixed the build of devel/kdevelop-base version 3.1.0 with latest
automake package version 1.9.1 installed.
|
|
it to ${CAT} as a fall-through.
|
|
PKG_DEFAULT_OPTIONS.
|
|
into the bsd.options.mk framework. Instead of appending to
${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes
the default options to be the union of PKG_DEFAULT_OPTIONS and any
old USE_* and FOO_USE_* settings.
This fixes PR pkg/26590.
|
|
|
|
|
|
before any @dirrm's are executed. Rather, put it explicitly at the top of
the final static PLIST generation code.
|
|
all of the .a, .la, .so, and .so.* files in the PLIST. This will
autogenerate the PLIST entries based on the informaion in the .la file.
This include print-PLIST support; if LIBTOOL_LA_FILES contains an
installed .la, its entries will be elided from the output PLIST template.
|
|
defined, note thatthe patch failure may be due to incompatible
build options and/or local patches, and suggest building with fewer.
|
|
|
|
|
|
|
|
|
|
|
|
that the whole pipeline returns 0. This avoids subtle breakage when the
we use built-in software and there is actually no list of files passed as
input to the pipeline, and the final egrep returns non-zero.
|
|
has a space in the filename. Without the quoting the buildlink
stage fails completely with errors. ok'ed by Johnny Lam.
|
|
|
|
remove rpath options come first. This fixes problems we may encounter
if ${_OPSYS_RPATH_NAME} is something surprising, like "-L". On Darwin,
this was causing -L/usr/lib to be stripped out of "-Wl,-L/usr/lib",
which left a bare "-Wl," on the command line.
|
|
case ${_OPSYS_RPATH_NAME} is something surprising, like "-L".
|
|
pass "-Wl,${RPATH_FLAG}..." to the linker, which can break the build
of these packages. Using -L essentially makes these arguments a no-op,
and fixes packages which were solely broken by this.
|
|
|
|
|
|
|
|
|