Next | Query returned 75 messages, browsing 21 to 30 | Previous

History of commit frequency

CVS Commit History:


   2014-03-03 05:50:47 by OBATA Akio | Files touched by this commit (1)
Log message:
LICENSE=modified-bsd
   2014-03-03 04:30:55 by OBATA Akio | Files touched by this commit (43)
Log message:
Just define PKGNAME and use it.
   2012-10-04 00:14:04 by Thomas Klausner | Files touched by this commit (36)
Log message:
Update for python25 removal.
   2012-09-12 01:19:40 by Aleksej Saushev | Files touched by this commit (60)
Log message:
"user-destdir" is default these days
   2012-04-30 15:59:39 by Greg Troxel | Files touched by this commit (2)
Log message:
Use " for PKGNAME_REQUIRED, so that ${pkg} is expanded.

Resolves at least some issues with finding the right pyNN-foo, when
replacing packages that don't match PYTHON_VERSION_DEFAULT.

(This was a stray change in my tree not committed for a while, but
it's been working ok.)

Now 0.24.1.
   2012-01-25 16:20:35 by Greg Troxel | Files touched by this commit (1)
Log message:
Add note about use of unsafe_depends_loose, from discussion with
obache@.

Note that there is an issue with unsafe_depends not getting set when
options change.
   2011-03-22 05:04:58 by OBATA Akio | Files touched by this commit (2)
Log message:
Pass MAKE_SET_VARS with environment variables instead of make flags,
or it will be passwd down to subsequent make (ex. installation of dependencies)
and result in unwanted behaviour.
   2010-12-20 16:39:09 by Greg Troxel | Files touched by this commit (2)
Log message:
0.23: Pass PKGNAME_REQD to make operations.

Set PKGNAME_REQD to give underlying make processes a chance to set
options derived from the package name.  For example, the appropriate
version of Python can be derived from the package name (so, when
building py25-foo, use python-2.5, not python-2.6).   Specifically,
  MAKE_SET_VARS='PKGNAME_REQD=${pkg}-*'

From Alan Barret via pkgsrc-users@.
   2010-12-20 16:24:25 by Greg Troxel | Files touched by this commit (2)
Log message:
0.22: Avoid infinite loop in some error cases.

Sometimes, the set of packages to be replaced ($REPLACE_TODO) does not
have any members which are installed (and hence in $TSORTED).  This
caused the loop over $TSORTED to not find any packages to replace.
The check for not having found one was missing, resulting in the last
package in TSORTED being replaced.  Because $REPLACE_TODO is still
non-empty, this repeats.

This patch adds an abort when no packages in $TSORTED are in
$REPLACE_TODO.  Analysis and patch from Ian D. Leroux on
pkgsrc-users@.
   2010-04-23 19:11:12 by Greg Troxel | Files touched by this commit (1)
Log message:
Start todo list for pkg_rolling-replace (not installed).

Next | Query returned 75 messages, browsing 21 to 30 | Previous