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

History of commit frequency

CVS Commit History:


   2008-04-16 07:42:46 by OBATA Akio | Files touched by this commit (2)
Log message:
Switch MASTER_SITES from dead sites to download.savvanah.nongnu.org.
Noticed by Zafer Aydogan via private mail.
distfile name is differ, but contents are same.
   2007-08-09 11:40:37 by Matthias Scheler | Files touched by this commit (1)
Log message:
Update the home page URL.
   2006-12-27 14:37:47 by Joerg Sonnenberger | Files touched by this commit (210)
Log message:
- fine grained X11 dependencies for packages which have either USE_IMAKE
  or USE_X11BASE set, but don't include mk/x11.buildlink3.mk directly or
  via buildlink3.mks
- introduce BUILDLINK_PREFIX.libXpm as alias for BUILDLINK_PREFIX.xpm
  in the !modular case
- fix some cases where the check for libX11 couldn't work at all by using
  C++ for compilation without including the proper headers

Verified using a full X11_TYPE=xorg bulk build without additional
breakage. Discussed with salo@, wiz@ and send to packages@ for feedback.
   2006-12-15 21:33:06 by Joerg Sonnenberger | Files touched by this commit (236)
Log message:
Mechanically replace all includes of buildlink3.mk of the following
packages with the modular Xorg equivalent. Those are falling back
to the old location by default, so this commmit doesn't change
dependencies.

graphics/xpm ==> x11/libXpm
fonts/Xft2 ==> x11/libXft
x11/Xfixes ==> x11/libXfixes
x11/xcursor ==> x11/libXcursor
x11/Xrender ==> x11/libXrender
x11/Xrandr ==> libXrandr
   2006-10-18 23:36:03 by Roland Illig | Files touched by this commit (1)
Log message:
Fixed PKGMANDIR.
   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-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-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.

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