Next | Query returned 280 messages, browsing 151 to 160 | Previous

History of commit frequency

CVS Commit History:


   2005-05-12 00:03:53 by Johnny C. Lam | Files touched by this commit (7)
Log message:
I mixed up MAKE_FLAGS with MAKEFLAGS.  The latter is what we actually use
to pass make flags to bmake.
   2005-05-09 07:14:09 by Johnny C. Lam | Files touched by this commit (7)
Log message:
Don't assign to PKG_OPTIONS.<pkg> which has special meaning to the
options framework.  Rename PKG_OPTIONS.* to PKG_BUILD_OPTIONS.*.
   2005-05-09 07:06:56 by Johnny C. Lam | Files touched by this commit (7)
Log message:
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that
caches variable definitions that were computed by make.  These variables
are specified by listing them in MAKE_VARS, e.g.,

	.if !defined(FOO)
	FOO!=	very_time_consuming_command
	.endif
	MAKE_VARS+=	FOO

bsd.pkg.mk will include only the one generated during the most recent
phase.  A particular phase's makevars.mk file consists of variable
definitions that are a superset of all of the ones produced in previous
phases of the build.

The caching is useful because bsd.pkg.mk invokes make recursively,
which in the example above has the potential to run the very time-consuming
command each time unless we cause FOO to be defined for the sub-make
processes.  We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't
consistently applied to every invocation of make, and also because
MAKE_FLAGS can overflow the maximum length of a make variable very
quickly if we add many values to it.

One important and desirable property of variables cached via MAKE_VARS
is that they only apply to the current package, and not to any
dependencies whose builds may have been triggered by the current
package.

The makevars.mk files are generated by new targets fetch-vars,
extract-vars, patch-vars, etc., and these targets are built during
the corresponding real-* target to ensure that they are being invoked
with PKG_PHASE set to the proper value.

Also, remove the variables cache file that bsd.wrapper.mk was generating
since the new makevars.mk files provide the same functionality at a
higher level.  Change all WRAPPER_VARS definitions that were used by
the old wrapper-phase cache file into MAKE_VARS definitions.
   2005-05-08 14:03:57 by Johnny C. Lam | Files touched by this commit (7)
Log message:
PKG_OPTIONS.<pkg> isn't a good approximation to PKG_OPTIONS for the
package because PKG_OPTION.<pkg> could contain negative options, which
are never part of PKG_OPTIONS.  Instead, use the show-var target to
display the value.  We cache it in WRAPPER_VARS and in MAKE_FLAGS to
prevent reinvoking the show-var target recursively.
   2005-05-04 15:45:51 by Mark Davies | Files touched by this commit (3)
Log message:
Previous patch introduced a regression, breaking reading of .rgb images
in most cases.
   2005-05-01 06:35:40 by Mark Davies | Files touched by this commit (9)
Log message:
Apply the official KDE patches for CAN-2005-1046.
http://www.kde.org/info/security/advisory-20050421-1.txt
Bump PKGREVISION.
   2005-04-29 01:39:35 by Johnny C. Lam | Files touched by this commit (1)
Log message:
Use :O instead of ${SORT}.
   2005-04-19 12:55:25 by Thomas Klausner | Files touched by this commit (2)
Log message:
Depend on xdg-dirs-1.2, and remove share/desktop-directories from
managed directories. Bump PKGREVISION to 2.
   2005-04-18 18:54:00 by Matthias Drochner | Files touched by this commit (2)
Log message:
Add an explicite check to a QImage construction. There is an inplicite
check, but it is not obvious whether it will catch all cases, in
particular with corrupted TIFF files. Was the last occurence of an
not-explicitely-checked QImage construction, so things are consistent now.
   2005-04-14 00:13:53 by Lubomir Sedlacik | Files touched by this commit (1)
Log message:
Bump BUILDLINK_RECOMMENDED for the latest security fix.

Next | Query returned 280 messages, browsing 151 to 160 | Previous