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

History of commit frequency

CVS Commit History:


   2006-10-12 10:56:56 by David Sainty | Files touched by this commit (1)
Log message:
Hmmm, revert previous for the moment.  'make show-var VARNAME=XML_ENTRIES'
with this change in-place suggests that sometimes the prefix IS added
in catalogs.mk (and presumably not in the client package, for some reason).
   2006-10-12 10:34:56 by David Sainty | Files touched by this commit (1)
Log message:
Don't pretend to automatically add ${PREFIX} to each XML_ENTRIES and
SGML_ENTRIES entry - it doesn't work.  Probably because expansion
in this context requires the variable to already be defined, which it
isn't.

This is lucky, because every package using catalogs.mk adds ${PREFIX}
itself to each entry.  So usually it gets added just the once.

The luck stops if you do something like: make PREFIX=/usr/pkgroot2

This makes the automatic ${PREFIX} insertion suddenly work AS WELL as
the client packages adding ${PREFIX} themselves.  We end up with
/usr/pkgroot2/share/xml/catalog containing lines like:

<nextCatalog \ 
catalog="/usr/pkgroot2/usr/pkgroot2/share/xml/docbook/4.3/catalog" \ 
/>

... after installing textproc/docbook-xml.  This in turn causes
textproc/scrollkeeper to obscurely fail to build at configure time.
   2006-07-09 01:11:17 by Johnny C. Lam | Files touched by this commit (877)
Log message:
Change the format of BUILDLINK_ORDER to contain depth information as well,
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.

For example, "make show-buildlink3" in fonts/Xft2 displays:

	zlib
	fontconfig
	    iconv
	    zlib
	    freetype2
	    expat
	freetype2
	Xrender
	    renderproto
   2006-07-09 00:39:49 by Johnny C. Lam | Files touched by this commit (877)
Log message:
Track information in a new variable BUILDLINK_ORDER that informs us
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
   2006-06-16 00:13:59 by Johnny C. Lam | Files touched by this commit (21)
Log message:
Pluralize INSTALL_TEMPLATE and DEINSTALL_TEMPLATE variable names as per
the pkglint warning:

    As {INSTALL,DEINSTALL}_TEMPLATE is modified using "+=", its name
    should indicate plural.

This does make the variables a bit more suggestive of the fact that they
hold lists of values.
   2006-04-12 12:27:47 by Roland Illig | Files touched by this commit (749)
Log message:
Aligned the last line of the buildlink3.mk files with the first line, so
that they look nicer.
   2006-04-06 08:23:06 by Jeremy C. Reed | Files touched by this commit (1147)
Log message:
Over 1200 files touched but no revisions bumped :)

RECOMMENDED is removed. It becomes ABI_DEPENDS.

BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.

BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.

BUILDLINK_DEPENDS does not change.

IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".

Added to obsolete.mk checking for IGNORE_RECOMMENDED.

I did not manually go through and fix any aesthetic tab/spacing issues.

I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.

I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.

As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.

As discussed on tech-pkg.

I will commit to revbump, pkglint, pkg_install, createbuildlink separately.

Note that if you use wip, it will fail!  I will commit to pkgsrc-wip
later (within day).
   2006-03-14 02:14:36 by Johnny C. Lam | Files touched by this commit (134)
Log message:
Modify the pkginstall framework so that it manages all aspects of
INSTALL/DEINSTALL script creation within pkgsrc.

If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts.  If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:

	INSTALL_SRC=	${PKGDIR}/INSTALL
	DEINSTALL_SRC=	# emtpy

As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts.  By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).

In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework.  The only public variables relating to the templates are:

	INSTALL_SRC		INSTALL_TEMPLATE
	DEINSTALL_SRC		DEINSTALL_TEMPLATE
				HEADER_TEMPLATE

The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
   2005-12-29 07:22:26 by Johnny C. Lam | Files touched by this commit (597)
Log message:
Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.
   2005-12-06 00:55:25 by Roland Illig | Files touched by this commit (413)
Log message:
Ran "pkglint --autofix", which corrected some of the quoting issues in
CONFIGURE_ARGS.

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