Age | Commit message (Collapse) | Author | Files | Lines |
|
Now the perl configure script finds a dlopen on SunOS and builds a shared
libperl, which makes it possible to build mod_perl.
|
|
|
|
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
|
|
before!)
|
|
package.
|
|
directly against -lperl when built. Combined with the previous update of
perl to add ${LOCALBASE}/lib to the rpath when creating shared
libraries/modules, these two changes make using mod_perl.so (ap-perl) more
painless. All perl shared modules now contain interlibrary dependencies to
the shared libraries they need. Instead of needing (at least on ELF):
LoadFile !/usr/lib/libm.so
LoadFile lib/perl5/5.6.1/i386-netbsd/CORE/libperl.so
...
# Any other libraries needed by perl shared modules need to listed
# with LoadFile here.
...
LoadModule perl_module lib/httpd/mod_perl.so
AddModule mod_perl.c
you'd need only the last two lines as the mod_perl authors intended.
I've tested this patch for many weeks now, successfully loading and using
the p5-Apache-ASP module as my test bed, and I haven't noticed any problems
with normal perl usage.
Also comment the Makefile slightly better.
|
|
If we're conflicting with mzscheme, it would help if we install mzscheme
and mzc as well.
|
|
If we're conflicting with mzscheme, it would help if we install mzscheme
and mzc as well.
|
|
installed files. We don't want buildlink references to escape into the
install directory.
|
|
linker rpath flag) deserves a bump in the package version number. Go to
perl-5.6.1nb5.
|
|
modules) about -Wl,-R. We cause -Wl,-R/path/to/libdir in LIBS settings
to now get propagated correctly to the link command for shared modules.
The rpath flag is also silently coerced to start with -Wl,-R or -R
depending on the contents of ${LDDLFLAGS} to deal with either cc or ld
being invoked.
|
|
this strongly buildlinked and provide a buildlink.mk for dependent packages
|
|
* Ensure that shared objects/libraries created by perl Makefiles include
the correct run-time library search path by also including the local
libraries directories. For example, shared objects are linked on ELF
platforms with "cc -Wl,-R/usr/pkg/lib -L/usr/pkg/lib", and not just
"cc -L/usr/pkg/lib" as before.
|
|
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
|
|
helps creating README's for them.
|
|
/usr/local/scripts and forces the scripts to be installed there if it
exists. We override this by explicitly setting "scriptdir" to
"${PREFIX}/bin". This should fix the problem noted in pkg/14050 by
Brian Stark <bpstark@pacbell.net>.
|
|
Python versions, to replace the bsd.python.mk eventually
|
|
1.3.1_01 build of the Sun JRE and JDK for Linux. No list of changes was
provided, but this has been tested to work with Konqueror to correctly
display the Yahoo! Bridge game applet.
|
|
that OS is used.
|
|
for Perl's configuration script as suggested by Johnny C. Lam in private
e-mail.
|
|
exists under SunOS.
|
|
be set to ${PREFIX}/java and runtime jre and buildtime jdk both work
|
|
problem reported in pkg/13663 by John Klos <john@sixgirls.org> where on
older (pre-current) NetBSD/vax, <ieeefp.h> exists but <machine/ieeefp.h>
doesn't, which was broken since <ieeefp.h> included <machine/ieeefp.h>.
|
|
|
|
which may form part of Perl or Python's future, into the NetBSD packages
collection.
Provided in PR 13933 by Chris Pinnock <cjep@interoute.net.uk>, tarted
up somewhat by me.
PARROT: A bytecode language possible to be used in the future by
Perl 6 and a Python.
The idea was originally an April fool's joke...
"What we're releasing today is a very, very early alpha of the Parrot
interpreter. At the moment, we have support for some simple
operations on integer, floating point and string registers, and the
ability to read in and execute bytecode. We also have an assembler
which can generate bytecode output from Parrot assembly."
|
|
include:
- Re-adding ${LOCALBASE}/include and ${LOCALBASE}/lib to the local compiler
search paths,
Other changes include:
- Migrating the setting to not install man3 pages from patch-ab into the
package Makefile so that they aren't installed across all pkgsrc platforms.
- Better document SYSLIBPATH.${OPSYS}.
|
|
WRKSRC= ${WRKDIR}
This is much cleaner, much more indicative of what happens, and removes
another of the negative definitions (NO_.* = value).
|
|
the HOMEPAGE variable for, as well as some grammar and spelling fixes.
|
|
<abs@formula1.com>.
|
|
tweeks, and a new autoconf build system.
The package now conflicts with any installed version of mzscheme as it
builds with, and installs its own.
|
|
|
|
perl mess I created a year ago and making this a vanilla perl installation
again, and explicitly setting the system library path so that /usr/local/*
doesn't appear anywhere.
The installed perl library now also includes CGI.pm-2.752. The www/p5-CGI
package installs in to ${PERL5_SITEARCH} so there is no conflict with the
"standard" CGI.pm.
|
|
tweeks, and a new autoconf build system.
The package now conflicts with any installed version of mzscheme as it
builds with, and installs its own.
|
|
|
|
Include a bugfix for lisp_LISP independently discovered by me that has
been pulled up to the automake-1-4 branch of automake cvs.
Changes are:
New in 1.4-p5:
* Allow AM_PROG_LIBTOOL again.
* Diagnose AC_CONFIG_HEADERS the same as AC_CONFIG_HEADER.
* Display distributed file list correctly in usage message.
* Allow numbers in macro names.
* Bugfixes.
New in 1.4-p4:
* Deal with configure.ac as well as configure.in -- this time for real!
* The version numbering system now allows three point version numbers,
such as 1.4.4, without thinking they are alpha release numbers.
New in 1.4-p3:
* Deal with configure.ac as well as configure.in.
* Don't complain if `version.texi' is included in multiple places.
New in 1.4-p2:
* Deal with AC_CONFIG_FILES from autoconf-2.50.
* Improvements to f77 support.
* DESTDIR now works for script targets.
* distcheck-hook works correctly.
New in 1.4-p1:
* The version numbering system now allows fork identifiers (such as
the p1 in this version of automake).
* Cope gracefully with various versions of libtool which may or may not
require ltconfig, ltcf-c.sh, ltcf-cxx.sh or ltcf-gcj.sh.
* Bugfixes.
|
|
|
|
|
|
|
|
comprehensible ChangeLog is unfortunately not available. Update submitted
by Greg A. Woods, in PR pkg/13775.
|
|
|
|
Notable changes are:
* Massive grammer / lexer / internals fixage
* Form work
* Form [MaxButton, MinButton, ShowInTaskbar,
BorderStyle, LinkTopic, StartupPosition]
* Menu fixage
* sub-properties
* handle control box
* Add shapes support
* FormItem work
* visibility work
* [DragMode]
* Textbox [MultiLine]
* Textbox [MaxLength, PasswordChar]
* Misc.
* File handling updates
* Print statement
* Leak fixes
|
|
|
|
doesn't conflict with an installed 2.0.x
|
|
not really necessary to strip dots from library names under Solaris it
makes the packages more compatible which should ease maintenance.
|
|
installation directory in case the package isn't installed.
|
|
${LOCALBASE} directories. Also set PKG_FC to the buildlink'ed f2c-f77
wrapper script.
|
|
to be an optimization bug that causes the build to fail (pkg/13395). The
problem appeared in the original PR on an Amiga running NetBSD 1.5.1 and
also on a mac68k running NetBSD 1.5.1. This workaround was tested on the
mac68k system (kindly provided by Jon Lindgren).
|
|
mostly bug fixes. (See release notes for details).
|
|
${LOCALBASE} in *_PREFIX definition.
|
|
for clarity.
|