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.
|
2006-02-06 00:11:50 by Joerg Sonnenberger | Files touched by this commit (4082) |
Log message:
Recursive revision bump / recommended bump for gettext ABI change.
|
2005-07-27 18:21:17 by Thomas Klausner | Files touched by this commit (31) |
Log message:
Reset MAINTAINER -- he stopped working on pkgsrc.
|
2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539) |
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.
|
2004-10-03 02:13:34 by Todd Vierling | Files touched by this commit (908) |
Log message:
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
2004-07-22 11:16:04 by Marc Recht | Files touched by this commit (123) |
Log message:
add python as category
ok'd a while back at pkgsrcCon by agc and wiz
|
2004-05-17 23:32:35 by Stoned Elipot | Files touched by this commit (26) |
Log message:
Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymore
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
|
2004-04-13 01:15:02 by Lubomir Sedlacik | Files touched by this commit (23) |
Log message:
Follow libogg into multimedia/.
|
2004-03-18 10:12:18 by Johnny C. Lam | Files touched by this commit (232) |
Log message:
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
|
2004-03-16 19:23:28 by Johnny C. Lam | Files touched by this commit (25) |
Log message:
If the ${PKGBASE} of a package doesn't match the token passed to
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that
we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
|