Age | Commit message (Collapse) | Author | Files | Lines |
|
Currently, the pkgviews/buildlink2 integration is incomplete. People who
work on this branch should also check out src/usr.sbin/pkg_install from
the pkgviews branch.
|
|
|
|
|
|
need to set USE_GCC_SHLIBS. we also don't need libiconv, libstdc++
or libm.
bump PKGREVISION.
|
|
libstdc++ in gcc3.
when defined, USE_GCC_SHLIB ensures that the correct rpath is passed
to the linker, and a full dependency on the compiler package is
registered.
packages which define USE_GCC_SHLIB should not include
mk/gcc.buildlink2.mk (or gcc{,3}/buildlink2.mk) as it is handled
automatically.
|
|
|
|
recent pkgrevision bump.
|
|
|
|
include it's buildlink2.mk.
bump PKGREVISION.
|
|
|
|
|
|
|
|
fixes runtime problem noted by zuntum.
- add MESSAGE.
|
|
|
|
|
|
bump dependency to latest libiconv version; recursively also bump all
dependencies of packages depending on libiconv.
Requested by fredb.
|
|
makes these packages build correctly on Darwin where perl>=5.8.0 is
required.
|
|
nb1 to the PKGNAME made it go nb1nb1...). Bump to PKGREVISION 2.
|
|
Dependency is picked up via the sablotron package, so just add to link.
Bump version to nb1, as old version will build correctly, but fail to link
into apache.
|
|
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
|
|
|
|
With this patch, the sablotron base URI for xslt processing is set to the
current working directory, so document inclusion (ala
<xsl:apply-templates select="document(data/test.xml)" />
) will DTRT.
Bump the pkg version to 1.1nb1, as stylesheets written for the new version
may not work with the old.
|
|
|
|
|
|
|
|
mod_xslt provides a simple, fast mechanism for doing XSLT transformations
of XML content for presentation to the user. It doesn't seek to provide
all the bells and whistles of, say, Cocoon, but being implemented natively
and using an XSLT parser (sablotron) which is implemented natively, it
provides a nice lightweight solution.
|