1.) It breaks the build of "www/firefox" which gets upset if "SHELL" is
not defined in the environment. There are probably more packages
which similar problems.
2.) It breaks established use case like this one:
export ALLOW_VULNERABLE_PACKAGES=yes
cd pkgsrc/multimedia/ffmpeg2theora
bmake install
In this case the value of "ALLOW_VULNERABLE_PACKAGES" will not be
passed to the build of "pkgsrc/multimedia/ffmpeg". And the build of
this package will fail due to known vulnerabilities.
`install' with USE_DESTDIR=yes.
This changes prevent to unwanted overwite of existing binary packages with
test installation (`stage-install', `replace' & `undo-replace', and so on).
To do both `install' and `package', you can still use `package-install' target,
same as USE_DESTDIR=no.
substitutions will not be correct.
Fixes issue with ABI=64 where /usr/lib/amd64 was being exposed, but
packages will need to be rebuilt for the change to take effect.
however that is not the case. To get that behaviour use ':S/c/ /g'.
Fixes a number of issues on various OPSYS introduced with the recent
COMPILER_* and SYSTEM_DEFAULT_RPATH abstractions.
It is used in limited case, and does not exist by default on some platforms.
proposed at over 30 months ago, and no negative feedback (only one request).
hierarchy.
This values should be generated from output of some commands,
but I cannot find the rule.
Tested on armel and x86_64 Debian GNU/Linux environment.
The values are shown in http://wiki.debian.org/Multiarch/Tuples .
Build depends are target packages that are needed at build-time for,
e.g., static libraries to link against, header files to include, &c.
Tool depends are native packages that are needed at build-time for,
e.g., compilers/linkers/&c. to run.
ok agc
The NATIVE_xyz versions are for packages that build tools that they
run natively but don't end up in the final product.
This is a provisional scheme -- it should be replaced eventually by
something more principled.
ok agc
is also start with "\n", but msgctxt is inserted before it, to avoid msgfmt(1)'s
format mismatch check (`msgid' and `msgstr' entries do not both begin with '\n')
instead of hard-coded /usr/include, /usr/lib, ... paths.
* allow empty BUILDLINK_PREFIX.${_pkg_}, for builtin packags not match such
model (Haiku's system headers and libraries are in different hier).
default value are _OPSYS_INCLUDE_DIRS, _OPSYS_LIB_DIRS and _OPSYS_DEFAULT_RPATH,
defined in mk/platform/${OPSYS}.mk.
(maybe defined with compiler/development tools specific variables).
ghostscript-agpl.
Reverts revisions 1.255 and 1.254
----------------------------
revision 1.255
date: 2013/03/16 23:03:33; author: dholland; state: Exp; lines: +3 -3
print/ghostscript -> print/ghostscript-agpl
----------------------------
revision 1.254
date: 2013/03/16 21:47:14; author: dholland; state: Exp; lines: +13 -3
Choose ghostscript package for ghostscript tools based on whether
gnu-agpl-* is in ACCEPTABLE_LICENSES.
This is mostly the same as the old ghostscript type logic that was
removed in version 1.223.
A major security issue fixed in this release, CVE-2013-1899, makes it possible for a connection request containing a database name that begins with "-" to be crafted that can damage or destroy files within a server's data directory. Anyone with access to the port the PostgreSQL server listens on can initiate this request.
Two lesser security fixes are also included in this release: CVE-2013-1900, wherein random numbers generated by contrib/pgcrypto functions may be easy for another database user to guess, and CVE-2013-1901, which mistakenly allows an unprivileged user to run commands that could interfere with in-progress backups. Finally, this release fixes two security issues with the graphical installers for Linux and Mac OS X: insecure passing of superuser passwords to a script, CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.
For Windows Vista or later, executable files including special keywords
(install, update, patch, and so on) in its name are expected as requireing
privileged permissions by default (UAC).
If not, it must be specified with manifest file, or it will be failed to
execute as "Permission denied".
Mac OS X Mountain Lion's "sed" will otherwise reject some patch files
(e.g. "pkgsrc/devel/libcfg+/patches/patch-ab") because of broken
UTF-8 encoding.
It would probably be better not to use the bundled "sed" under
Mac OS X Mountain Lion at all. But it seems that this is not
supported by "pkgsrc" at the moment.
Mac OS X Mountain Lion. "/usr/X11" is only a symbolic link. Use the correct
path because buidlink3 will otherwise filter out "-I/opt/X11/include" which
causes build failures of e.g. the "cairo" package.
- remove LIBXAW variable. It is handled by buildlink3.mk now
- simplify patches and Makefile in packages using libXaw
- in some cases force use of Xaw3d (won't build with Xaw)
- replace some directly included of x11/Xaw3d with mk/xaw.buildlink3.mk
In next part:
- replace more includes with mk/xaw.buildlink3.mk
turned off in www/curl.
Modify the curl package to be aware of the libidn option. Ensure default
is on.
No functional change, so no version number bump.
DragonFly has two compilers in base, GCC 4.4.7 and GCC 4.7.2.
The way one switches between them for userland programs is to set
CCVER in the environment.
However, to set this via make.conf is tricky. I've been using the
low level "ALL_ENV+= CCVER=gcc47", but this trick fails to properly
identify the compiler which results in _GCC_VERSION being incorrectly
defined.
Additionally, there are some prominent packages that do not build on
gcc 4.7 and the fix is either not fully understood or would require a
large amount of work to implement. In these cases, it is desireable
to specify the package be built on gcc 4.4 regardless of CCVER setting.
To address these issues, a new directive is added: DRAGONFLY_CCVER.
It is only effective if OPSYS equals "DragonFly", and it will properly
set CCVER and properly define _GCC_VERSION. It will also allow a
per package specification of a particular compiler in the pkg makefile.
By default pkgsrc uses LOCABASE/gnu as a prefix for packages to install
native versions of GNU tools, which are them symbolically linked back to
the 'g' versions of the files in LOCALBASE, and users can then add
LOCALBASE/gnu/bin to PATH to pick up those tools.
On systems where the GNU environment is desired, PKGGNUDIR now allows
users to install the non-'g' files directly into LOCALBASE, making them
the default without having to alter PATH, whilst retaining the 'g' files
in order to ensure dependencies and tool paths remain the same.
This change modifies the algorithm used to keep track of the files that
have not yet been checksummed to use a simple loop instead of shell pattern
matching.
For packages with few distinfo entries, either way yields the same result
as the list of files to check is very short. But for those packages with
hundreds of distinfo entries (vim, I'm looking at you), the difference is
huge. In my old macppc machine, the checksum of vim used to take around
40 minutes and now it takes ~35 seconds. The difference is also clearly
visible in my faster amd64 machine (although I haven't bothered to time it).
Introduce USE_GCC_RUNTIME for packages which build shared libraries, but
do not use libtool to do so, and add logic to always define _USE_GCC_SHLIB
on Solaris if either USE_LIBTOOL or USE_GCC_RUNTIME are defined. On Solaris,
a non-GNU linker is always used, so this correctly adds a dependency upon the
gcc runtime for those packages.
"yes" or "no" for whether BUILDLINK_{INCDIRS,LIBDIRS,RPATHDIRS}.<pkg>
should automatically be added to the compiler/linker search paths.
Defaults to "yes".
DragonFly has NetBSD's librefuse so it can use NetBSD's FUSE
configuration, with the caveat that -lpuffs be provided wherever
lrefuse (or transformed -lfuse) is used. With this patch,
DragonFly 3.x can build several FUSE packages out of the box.
- Add mount for /usr/X11.
- Add support for mounting read-write directories, adding the postfix data
directory so that bulk builds can send mail.
- Use $kernel rather than rolling our own copy.
All recent packages featuring Ada code have a hard dependency on the
lang/gnat-aux compiler package. The valid values for USE_LANGUAGES
are c, c99, c++, fortran, fortran77, java, objc, so specifying a
specific compiler was necessary up into now.
One problem with lang/gnat-aux is that it is installed at ${LOCALBASE}
where the lang/gccXX compilers are installed at ${LOCALBASE}/gccXX.
The latter compilers have no possibility of sharing conflicting files
unlike lang/gnat-aux. Rather than fundamentally update the GCC 4.6-based
lang/gnat-aux to avoid these conflicts, a new Ada-capable compiler
based on GCC 4.7 was created with the intent of being supported by
mk/compiler.mk and mk/compiler/gcc.mk.
The Ada packages will be effectively migrated from lang/gnat-aux to the
new lang/gcc-aux compiler, but lang/gcc-aux will remain as a standalone
package as it is the only GCC 4.6-based compiler that builds on
DragonFly and serves it as a world and kernel compile option.
In addition to the current language wrappers, lang/gcc-aux adds
wrappers for "ada" (unique to gcc-aux, hardlinked to gcc driver),
and the gnat, gnatmake, gnatbind, gnatlink, gnatchop, gnatprep,
and gnatls programs. Supporting all of these allows the wrapper
system to be used with Ada packages; currently wrappers are mostly
disabled on them.
The lang/gcc47 implicitly adds support for the "objc-c++" language by
adding it to the USE_LANGUAGES list, but it wasn't really supported.
An attempt was made to better support objc-c++, but this new enumeration
probably still needs work or needs to be removed completely.
Logic for Ada support:
1) All lang/gccXX compilers have version numbers ranging from 2.8.1 to 9.
2) lang/gcc-aux uses the release date as its version number in the form of
YYYYMMDD with a minimum value of 20120614, so there is no version
overlap.
3) When at least one element of USE_LANGUAGES is "ada", the value of
20120614 is added to the set of GCC_REQD which selects lang/gcc-aux.
4) The _NEED_NEWER_GCC check is disabled. It fails and isn't relevant;
unless a package sets GCC_REQD over 20120614, the only way to select
lang/gcc-aux is to specify the Ada language and only one compiler
known to gcc.mk can support it.
OSX hasn't included the ability to loopback mount for a while, so introduce
NFS support, configurable via a new --mounthost option, and add additional
directories required for proper support.
This mostly works, however something is causing name lookups to fail in the
chroot and it will currently only look at /etc/hosts. Clue appreciated here.
Also fix /dev mounting/unmounting from the sandbox script.
systems which share the same base system but offer contrasting environments,
for example the various illumos forks which all identify as "SunOS 5.11".
Detect SmartOS and set OS_VARIANT accordingly.
where software assumes features of the native 'tar' and break when 'tar' is
the NetBSD version.
We are too close to the pkgsrc-2012Q2 branch to remove NBPAX_PROGRAM_PREFIX
completely, but if it's apparent that no platforms need to override this
default then it will be removed completely for the next branch.
For a long time, the norm in pkgsrc was that packages had an option
for IPv6 support "inet6", and this was not in PKG_SUGGESTED_OPTIONS.
On NetBSD (and probably other BSD), USE_INET6 was defined in system mk
files, and pkgsrc noticed this and enabled the inet6 option globally.
But, in some environments, this did not happen.
The inet6 option has been added to PKG_SUGGESTED_OPTIONS for almost
all packages. This change decouples IPv6 support in pkgsrc from the
base system.
People building on systems that do not support IPv6, or who do not
want IPv6 support in packages, can add
PKG_DEFAULT_OPTIONS+= -inet6
to mk.conf.
(Discussed for the last week on various lists, and ok wiz@.)
On DragonFly, packages like devel/doc++ and net/wap-utils were failing the
file check during installation due to a present locale.alias file. Treat
it the same as charset.alias.
static library for compatibility reasons. If a libtool library is linking
against -ldl, libtool only builds it statically because there is no
libdl.so. This prevented, at least, the build of devel/gobject-introspection.
Add it globally because there is no reason anyone would want to link against
libdl on MirBSD.
but apparently does not work.
I'm seeing two different problems on different machines, one where it
can't find classes in jar files that are clearly there and one where
it can't run even a trivial program without dying with a stack
overflow.
Also add a note
# XXX: Why are we looking in '/usr/lib${ABI}' and '/lib${ABI}', as we should
# XXX: only be looking in '/usr/lib${LIBABISUFFIX}' and '/lib${LIBABISUFFIX}'
