PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
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).
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD
when determining whether the native makeinfo can be used.
* Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo.
* Get rid of all the "split" argument deduction for makeinfo since
the PLIST module already handles varying numbers of split info files
correctly.
NOTE: Platforms that have "makeinfo" in the base system should check
that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are
correct.
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.
the appropriate tool via USE_TOOLS (usually "gs:run"), and remove
ghostscript.mk. This change removes a rather out-dated file from
pkgsrc and switches packages to use the more compact implementation
of the Ghostcript-handling inside the tools framework.
argument to the configure script to point to ${PREFIX}/info; otherwise
they'd get installed in the lilypond/lilypond subdirectory, thus being
unrecognized by the PLIST. Bump PKGREVISION to 2.
This represents a major version bump and with it many many improvements
and changes which are far to long to summarize here. One important change
is that this version works with gcc3.
Unfortunately, guile{,14}/buildlink3.mk directly includes it, and I don't
know which dependencies actually need libltdl, so it was a recursive bump.
Hopefully this recursive inclusion can be ripped out of
guile{,14}/buildlink3.mk at some point and bubble down to dependencies that
actually use libltdl, avoiding this headache in the future....
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.
- teTeX 1.0.x packages have been moved to teTeX1* directories.
- teTeX 2.0.x packages have been moved to teTeX* directories and their base
name has been changed to teTeX (instead of teTeX2).
extension Makefile fragments, because they really don't have anything to
do with the buildlink[12] frameworks. Change all the Makefiles that use
application.buildlink.mk and extension.buildlink.mk to use application.mk
and extension.mk instead.
Major news for the 1.4 releases:
DESIGN
* More pervasive GUILE integration resulting in improved design and
implementation. LilyPond is smaller, cleaner, more flexible, etc.
- Improved speed with comparable memory footprint
- More tweakability using less memory with the new `property push'
mechanism.
- Improved robustness: Lily almost never crashes.
- Access to internal music representation
* New font selection scheme similar to Latex-NFSS.
* Flexible formatting mechanism for musical texts.
* Chordnames are now configurable in every respect
* Part combining for orchestral scores and hymns: two voices are
combined into a staff automatically, including Solo/a2
indications as appropriate.
ERGONOMICS
* Point and click functionality using emacs and Xdvi.
* Rewritten Emacs mode
* Cleaned up syntax details
* Comprehensive documentation, including a rewritten tutorial.
* All properties have doc strings, and internal documentation is
generated automatically.
* Windows point-and-click installer
NOTATION FEATURES
* Piano pedals, Arpeggios, Glissandi, many more note head
shapes, Medieval clefs, custodes.
* Better lyrics placement: Automatical phrasing, melisma alignment,
and stanza numbering.
* Typography: More elegant slurs, aligned dynamics, text crescendos,
* Easy-play note heads
* ASCIIScript: ASCII-art output
* Improved standalone postscript layout.
IMPORT/EXPORT
* dynamics, tempo changes in the MIDI output
* Finale (.etf), PMX, Musedata and Mup import tools.
MISCELLANEOUS
* Mutopia ports collection: easily accessible music archive.
* Translations into Japanese, French and Russian
* Many many many bugfixes.
