| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
reported by Lars Nordlund via tech-pkg@.
|
|
They are needed in the fetch-list case to prevent outputting anything if
the distfile is allready in $DISTDIR.
|
|
|
|
lib/libecpg.so.5.0.0 not lib/libecpg.so.5.0
|
|
for many "core" modules, UTF-8 and Unicode bugfixes, and ithreads
bugfixes.
The major changes are in the pkgsrc infrastructure to handle Perl and
Perl modules. All pkgsrc-installed Perl modules are now installed in
"vendor" directories, and the perl interpreter has been modifed to
search for libraries in the following order: site, vendor, perl. The
Perl library is stored in a directory that is named for the Perl ABI
version associated with the Perl release, so any updates of Perl to
newer versions can be done "in-place" as long as Perl ABI version
remains the same. All Perl scripts and man pages are stored in
locations that won't conflict between site, vendor, and perl modules,
and a new utility perllink(1) now manages symlinks to those scripts
and man pages under the usual ${LOCALBASE}/bin and ${LOCALBASE}/man/man1.
PERL5_SITEPREFIX may be set to the prefix where local, site-specific
modules will be installed, e.g. PERL5_SITEPREFIX=/usr/local. Note
that modules installed here are completely unmanaged by pkgsrc.
Update the buildlink and tool dependencies on perl to require perl>=5.8.7
to reflect the new locations for Perl modules and the Perl shared
library.
|
|
PIC code archive, but libtool isn't smart enough to realize it. Munge
the name within cmd-sink-libtool into something that will make libtool
recognize it as a PIC code archive. We unmunge it in arg-pp-main so
non-libtool wrappers see the right thing. This let's us use libtool
to link applications with an embedded Perl interpreter.
I feel so dirty...
|
|
|
|
martii on tech-pkg.
|
|
|
|
outputs 2, but 0 would be expected. That means that the arguments to set
-- must never be empty. I added the necessary checks. I also used
for...done loops instead of set, as they are simpler and don't use
global variables.
|
|
function that does the same. The Solaris /bin/sh does not know this type
of substitution. Now we could only have problems with /bin/sh which do
not know functions, but as we are using shell functions in many other
places, this should be fine.
|
|
|
|
|
|
|
|
pkgsrc/mk/defaults/mk.conf.
This is from PR 30741 from anonymous AT example.net.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
branch.
|
|
|
|
|
|
testcase (bug2) for regress/make-quoting.
|
|
failure of audio/bmp. This needs to be investigated further. See the
comment in the file.
|
|
This is a return to the behavior that we had prior to revision 1.5.
|
|
dependency on groff just for tbl(1) when available in the base system.
also, add .if exists() around nroff(1) because SUNWdoc is optional.
|
|
it is correctly defined in tools.Darwin.mk and tools.Linux.mk.
|
|
config files, directories, rc.d scripts, etc., use relative paths as
much as possible to avoid hard-coding the ${PREFIX}-location in which
the files should be installed. Where full paths are specified, if
the path is within ${PREFIX}, then automatically strip off the ${PREFIX}
part when creating the entries for the helper scripts. Also, modify
the helper scripts to understand that relative paths should be considered
to be relative to ${PKG_PREFIX}.
|
|
+SHELL.
* Turn PKG_REGISTER_SHELLS into a variable that can be set in the shell
environment so that admins can make a choice when installing from
binary packages.
* PKG_SHELL is now a list of paths, and if the path is relative, then it
is taken to be relative to ${PREFIX}. Convert packages that set
PKG_SHELL to take advantage of this new feature by changing the full
paths to the shells into relative paths.
|
|
|
|
want to be seen over and over again each time that file is included.
This stops us from appending the same bits over and over again to
CONFIGURE_ARGS and to X11_LDFLAGS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on Solaris.
|
|
if an untested command fails (see sh(1), "-e errexit"). Do this by
changing lines that look like:
test expression && command
to
test ! expression || command
so that the statement list always returns 0. Also, back out revision
1.38 of pkgsrc/mk/install/install and modify the if-test to branch
correctly if +USERGROUP doesn't exist.
|
|
no user or group needs to be created. This fixes PR pkg/30849 by myself.
|
|
are specified, then don't create +USERGROUP, etc.
|
|
Based on suggestion by Matthias Drochner.
|
|
|
|
set must be selected, requested and reviewed by wiz:
PKG_OPTIONS_NONEMPTY_SETS
This is a list of names of sets of options. At
least one option from each set must be selected.
The options in each set are listed in
PKG_OPTIONS_SET.<setname>. Options from the sets
will be automatically added to PKG_SUPPORTED_OPTIONS.
|
