Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on May 4, 2011
  1. Also set `package-install' to UPDATE_TARGET/DEPENDS_TARGET if current…

    obache authored
    … target is
    `package-install', to indirect dependency also create binary package with
    `make package' or `make package-install'.
    should fix PR#44857.
Commits on Jul 3, 2010
  1. The "-p" option is redundant as it is included in the MKDIR variable.

    darcy authored
    As discussed with joerg@.
Commits on Jun 15, 2010
  1. Apply my fix for PR 35091: do a check-vulnerable step first in "make

    dholland authored
    update", so if it's going to fail because of a known vulnerability it
    does so before uninstalling anything. I've been carrying this patch
    for some three years with no ill effects. Ok by agc@.
Commits on Feb 25, 2010
Commits on Feb 19, 2010
Commits on May 16, 2009
  1. Don't require pkg_delete or pkg_info -r to list packages in full

    joerg authored
    topological sort for the make update list. This breaks naturally when
    new dependencies are introduced that are also in the list scheduled for
    later installation. Reported by David Holland.
Commits on Mar 7, 2009
  1. make update might be called without having the package installed, so

    joerg authored
    check for the presence before trying to extract dependencies.
Commits on Mar 5, 2009
  1. Use pkg_info -r if present and fall back to pkg_delete for pkg_install

    joerg authored
    before 20090225. Intermediate versions get an explicit error.
    The building of the recursive dependency was broken as the new
    pkg_delete would stop without recursing and the target dependend on that
    behavior. Reported by David Holland.
Commits on Apr 7, 2008
Commits on Feb 7, 2008
  1. Replaced _PKG_SILENT and _PKG_DEBUG with RUN.

    rillig authored
Commits on Sep 7, 2007
  1. Replaced ${_PKG_SILENT}${_PKG_DEBUG} with ${RUN}, since it is shorter.

    rillig authored
    Removed unnecessary braces around a single pipeline. Also removed the
    ||true, since awk is very unlikely to fail.
  2. Correct typo, really fixes PR 36940.

    obache authored
Commits on Sep 6, 2007
  1. One line of code can say as much as ten.

    rillig authored
Commits on Oct 5, 2006
Commits on Jul 27, 2006
  1. Whenever we invoke a recursive make, we need to ensure that the proper

    jlam authored
    environment ${PKGSRC_MAKE_ENV} is also passed along.  Create a
    convenience variable RECURSIVE_MAKE that does exactly this and that
    can be used in place of MAKE when invoking make recursively.
    Use RECURSIVE_MAKE everywhere in pkgsrc/mk that we invoke make
Commits on Jun 7, 2006
  1. 1.) Remove all instances of '@${WARNING_MSG} "Warning: ...' which res…

    tron authored
        in error message like 'WARNING: Warning: ...'.
    2.) Replace "WARN_MSG" with "WARNING_MSG" which makes the "make package"
        target work again for restricted packages like "acroread7".
Commits on Jun 5, 2006
  1. Move definitions for UPDATE_TARGET and DEPENDS_TARGET closer to where

    jlam authored
    they are used.  Also, move UPDATE_RUNNING into the install module where
    it is used, and make it "private" by prepending with an underscore.
Commits on Jun 4, 2006
Commits on Jun 3, 2006
  1. First pass at implementing support for package system flavors other

    jlam authored
    than pkgsrc's current one.  This is an important lead-up to any project
    that redesigns the pkg_* tools in that it doesn't tie us to past design
    (mis)choices.  This commit mostly deals with rearranging code, although
    there was a considerable amount of rewriting done in cases where I
    thought the code was somewhat messy and was difficult to understand.
    The design I chose for supporting multiple package system flavors is
    that the various depends, install, package, etc.  modules would define
    default targets and variables that may be overridden in files from
    pkgsrc/mk/flavor/${PKG_FLAVOR}.  The default targets would do the
    sensible thing of doing nothing, and pkgsrc infrastructure would rely
    on the appropriate things to be defined in pkgsrc/mk/flavor to do the
    real work.  The pkgsrc/mk/flavor directory contains subdirectories
    corresponding to each package system flavor that we support.  Currently,
    I only have "pkg" which represents the current pkgsrc-native package
    flavor.  I've separated out most of the code where we make assumptions
    about the package system flavor, mostly either because we directly
    use the pkg_* tools, or we make assumptions about the package meta-data
    directory, or we directly manipulate the package meta-data files, and
    placed it into pkgsrc/mk/flavor/pkg.
    There are several new modules that have been refactored out of
    as part of these changes: check, depends, install, package, and update.
    Each of these modules has been slimmed down by rewriting them to avoid
    some recursive make calls.  I've also religiously documented which
    targets are "public" and which are "private" so that users won't rely
    on reaching into pkgsrc innards to call a private target.
    The "depends" module is a complete overhaul of the way that we handle
    dependencies.  There is now a separate "depends" phase that occurs
    before the "extract" phase where dependencies are installed.  This
    differs from the old way where dependencies were installed just before
    extraction occurred.  The file is now replaced by
    a script that is invoked only once during the depends phase and is
    used to generate a cookie file that holds the full set of reduced
    dependencies.  It is now possible to type "make depends" in a package
    directory and all missing dependencies will be installed.
    Future work on this project include:
        * Resolve the workflow design in anticipation of future work on
          staged installations where "package" conceptually happens before
        * Rewrite the buildlink3 framework to not assume the use of the
          pkgsrc pkg_* tools.
        * Rewrite the pkginstall framework to provide a standard pkg_*
          tool to perform the actions, and allowing a purely declarative
          file per package to describe what actions need to be taken at
          install or deinstall time.
        * Implement support for the SVR4 package flavor.  This will be
          proof that the appropriate abstractions are in place to allow
          using a completely different set of package management tools.
Something went wrong with that request. Please try again.