Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This is needed for databases/py-psycopg at least to compile properly.
Since the installed version changed, bump revision.
|
|
prerequisite libraries at runtime.
fixes build on Solaris (and probably others).
|
|
it was broken because the delimeter , can appear in the RHS of the
sed(1) expression (think "-Wl,-R ..."), and it does nothing useful
because the patterns don't appear in the files.
|
|
structure padding is used
not application relevant, so I abstain from bumping PKGREVISION
|
|
|
|
|
|
bin/python wrapper. Bump their PKGREVISION to 1.
Also remove the python package. In order to preserve a similar behavior to
this one using the new framework, start by installing pkg_alternatives.
Then just open its manpage, scroll down to the EXAMPLES section, Applying
filters subsection, and follow the (rather short) directions given there.
|
|
|
|
Suggested by Roland Illig, ok'd by various.
|
|
|
|
* Add a db1.builtin.mk file that detects whether DB-1.85 functionality
exists in the base system, and remove the distinction between
"native" and the other Berkeley DB packages -- we now refer to
db[1234]. This paves the way for any future databases/db1 package.
* USE_DB185 shouldn't need to be set by any packages -- its correct
value is now automatically determined by bdb.buildlink3.mk depending
on whether we explicitly request db1 or not. By default, if you
include bdb.buildlink3.mk, you want DB-1.85 functionality and
USE_DB185 defaults to "yes", but if you explicitly remove db1 from
the list of acceptable DBs, then USE_DB185 defaults to "no".
* Set BDB_LIBS to the library options needed to link against the DB
library when bdb.buildlink3.mk is included.
* We only add the DB library to the linker command automatically if
we want DB-1.85 functionality; otherwise assume that the package
configure process can figure out how to probe for the correct
headers and libraries.
Edit package Makefiles to nuke redundant settings of USE_DB185.
|
|
patch based upon the one Georg Schwarz provided in PR pkg/27402
|
|
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
|
Bump PKGREVISIONS accordingly.
|
|
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.
|
|
ok'd a while back at pkgsrcCon by agc and wiz
|
|
Noted by Georg Schwarz on tech-pkg@.
|
|
|
|
Buildlink files: RECOMMENDED version changed to current version.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
and any pre-existing buildlink2.mk files.
|
|
|
|
python20 to python20-2.0.1nb6
python21 to python21-2.1.3nb2
python21-pth to python21-2.1.3nb4
python22 to python22-2.2.3nb1
python22-pth to python22-2.2.3nb1
python23 to python23-2.3.3nb1
python23-pth to python23-2.3.3nb1
|
|
* Use BUILDLINK_{INCDIRS,LIBDIRS}.<pkg> instead of using
BUILDLINK_{CPPFLAGS,LDFLAGS}.<pkg> since we're just dealing with adding
directories to the various search paths.
|
|
|
|
|
|
|
|
|
|
patches we've applied to Python-2.1+
|
|
|
|
environment
|
|
so that dynamic libraries using libgcc functions can be loaded
should fix PR pkg/16144 by Brett Slager
|
|
|
|
Makefiles simply need to use this value often, for better or for
worse.
(2) Create a new variable FIX_RPATH that lists variables that should
be cleansed of -R or -rpath values if ${_USE_RPATH} is "no". By
default, FIX_RPATH contains LIBS, X11_LDFLAGS, and LDFLAGS, and
additional variables may be appended from package Makefiles.
|
|
|
|
Unconditionally compile in SSL support; bump PKGREVISION.
|
|
to BUILDLINK_FILES.<pkg>.
|
|
|
|
|
|
these python packages is empty.
|
|
the PLIST is created at install time; thus, add all files to link in here
by hand.
|
|
as to find their headers and libraries. Also allow "-lpython" to resolve
to the versioned libpython (-lpython2.2, etc.).
|
|
assume all of those headers belong to the python package. We use the trick
for kdelibs2 and generate the BUILDLINK_FILES list from the PLIST.
|
|
python/pyversion.mk in particular.
|
|
embedding friendly, as suggested in PR pkg/14520 by Jarkko Torppa
-having to touch Setup.in anyway, comment out the non-64-bit-clean
modules regularily and remove the Makefile magic which led to the
same effect
|
|
on any platform (we can make a separate pkg for it later)
-pull in a patch which used to be in devel/py-readline here because
it is Python version specific
-bump PKGREVISION
|
|
It doesn't work with anything but Python-2.0 anyway, and will die soon.
|
|
python version,
bump pkg revision
|
|
directory
let it conflict with the old pkg, don't install files which might
conflict with other versions
|