pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

pkgsrc-2015Q2 released

The pkgsrc team is proud to announce the availability of the
pkgsrc-2015Q2 branch.  We welcome mariadb-5.5.43, attic 0.16, Mesa
10.5.7, emacs 24.5, boost 1.58.0, xfce 4.12, many new packages from
texlive-2015, perl-5.22, and firefox 38.0.5. 
Number of Packages
In pkgsrc, there are:
16432 possible pkgsrc packages in pkgsrc-2015Q2 (15246 last quarter)
15947 binary packages built with clang for NetBSD-current/x86_64 (14896 last quarter)
14147 binary packages built with gcc for SmartOS/x86_64 (13092 last quarter)
14064 binary packages built with gcc for SmartOS/i386 (13028 last quarter)
14054 binary packages built with clang for FreeBSD 10.1/x86_64 (12802 last quarter)
12596 binary packages built with gcc for DragonFlyBSD 4.1/x86_64
11445 binary packages built with gcc for Darwin 10.8.0/i386 (10019 last quarter)
10054 binary packages built with gcc for Darwin 8.11.0/powerpc (11224 last quarter)
In addition, this quarter:
1155 packages have been added (216 last quarter)
4 packages have been renamed, 3 moved (2 last quarter)
27 packages removed, 12 with a successor (46 and 11 last quarter)
2015 packages updated (2007 last quarter)

Pkgsrc Release Schedule
The pkgsrc developers make a new release every three months.  We
believe that this is a sweet spot between too many updates, and
keeping abreast of issues like security vulnerabilities.  Pkgsrc is
not tied to any one operating system or architecture, which gives us
the ability to decouple the releases from any operating system
releases, and to concentrate on the packages themselves.
This is the 47th quarterly release of pkgsrc.
Changes to pkgsrc

Preliminary support for Bitrig was added.

Many pkgsrc developers and contributors have all helped
with PR submissions, fixes and bug reports.
Package Additions
Hundreds of texlive 2015 packages have been added.

xfce was updated to 4.12, bringing in additional xfce packages.

Package Removals
We actively manage the packages in pkgsrc, and delete ones that
are no longer useful relative to maintenance costs.  We said goodbye
to python26.
One neat feature of pkgsrc is its ability to sort package versions
based on the version numbers.  It's used in audit-packages, to report
on any installed packages which may have security vulnerabilities in
them. maintains lists of vulnerable
packages, along with reference URLs relating to the exposure.  We
thank the whole pkgsrc-security team for their hard work.  Sample
output from audit-packages is shown below:
% audit-packages
Package wireshark-1.10.14nb1 has a multiple-vulnerabilities vulnerability, see
Getting pkgsrc
More information can be found in
tar files for pkgsrc, along with checksums, can be found at
and anonymous cvs can be used:
        cvs -z3 -q -d checkout -r pkgsrc-2015Q2 -P pkgsrc
or by pulling from the git mirror at:
or the mercurial mirror at:

Joyent provide quarterly binary package sets for SmartOS/illumos,
OS X, and Linux, as well as some quickstart documentation at:
The packages are built from their pkgsrc fork available at:
which includes support for experimental features such as
multiarch packages, but may lag behind the git mirror.
About pkgsrc
pkgsrc is a cross-platform packaging system.  It allows people to
download sources and to build and install binary packages on one or
more platforms.
Building packages from source is useful for a number of reasons:
+ not only is the provenance of source code checked (by using multiple
digests), with pkgsrc, the version of source code you are working
with is the same that other developers and users have.
+ package builders can choose to customize their own installations by
means of the option framework.  pre-built packages from other builders
may not have specified the same options.
+ patches are maintained in a central repository, and, again, are
checked at patch application time by using digests. The patches
which are applied to the sources being built are the same ones which
are known to be used and proved by other pkgsrc users (not necessarily
on the same platform).
+ by building from source, all doubts about compilers, build practices,
source code cleanliness, and packaging differences are removed. 
Digital signatures of binary packages, while useful in themselves,
only prove certain aspects of binary package provenance. (pkgsrc has
had signed packages since 2001.)
+ it may be difficult or impossible to find a pre-built package for
the operating system or architecture.
+ a pre-built package may have further or conflicting pre-requisites,
which are themselves difficult to find or build. By building everything,
including pre-requisites, a from-source packaging system can ensure
that pre-requisites are present and integrated.
At the present time, pkgsrc supports 23 platforms:
        Darwin/Mac OS X
        SCO OpenServer
Complete dependency and pre-requisite package information is held and
used by the package management software - if packages rely on other
packages to function properly, that pre-requisite will be built,
installed and managed as part of the package installation process. 
Binary packages can be managed using pkgin and nih.
Thomas Klausner
On behalf of the pkgsrc developers
Sat Jul  4 17:16:17 CEST 2015

Home | Main Index | Thread Index | Old Index