• http://download.linuxaudio.org/lilypond/sources/v2.18/ (Download)

• (2014-05-28) Updated to version: lilypond-2.18.2
• (2011-08-23) Updated to version: lilypond-2.14.2
• (2011-07-06) Updated to version: lilypond-2.14.1
• (2011-05-15) Updated to version: lilypond-2.12.3
• (2010-11-14) Package deleted from Ports
• (2010-01-01) Updated to version: lilypond-2.12.3
• (2009-10-12) Updated to version: lilypond-2.12.2
• (2007-09-24) Updated to version: lilypond-2.10.33
• (2007-06-07) Updated to version: lilypond-2.10.25
• (2007-04-13) Updated to version: lilypond-2.8.8

Log message:
replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes

Log message:
Update gettext to 0.20.1.
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext       -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new)                  devel/gettext,-textstyle

Log message:
mftrace moved from fonts/ to print/

Log message:
Add COMPILER lines to c++ ports which currently use the default. Adjust
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.

Log message:
bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports.

Log message:
use COMPILER_LIBCXX where applicable

Log message:
use LIBCXX

Log message:
drop SHARED_ONLY from python and ruby ports

Log message:
Cope with recent fonts directory change in ghostscript.
ok kili@

Log message:
Tests had been "temporarily" disabled for more than three years
now, so just drop all the test-goo.

Log message:
adjust dependencies after moving fonts to fonts/
pointed out by sthen@

Log message:
Remove BROKEN-hppa, the last version builds fine there.
Tested by myself, committing on behalf of kili@

Log message:
Matt doesn't want credits any longer.

Log message:
Update to lilypond-2.14.1.
This still uses the downloaded documentation instead of building
it, because it's no fun do build the documentation on low-memory
and/or slow systems like arm (it ran for a couple of days on my
armish, and then it failed with a segfault, which i then couldn't
reproduce for the specific file the segfaults happend on).
It also doesn't depend on the texinfo-4.13 port I sent to ports@
(but not yet committed) recently.
Running it on some of my (rather oldish, i.e. written for lilypond-2.10
and older) files produces mixed results -- simple stuff still works,
some stuff reports failure (yet creates correct output, which is
strange).  Complicated music like my (never finished) work on the
Busoni transcription of BWV-1004/Partita II doesn't work at all
(but iirc, it didn't with lilypond-2.12, either).
make regress currently fails with this version, because it would
need the texinfo port and a new test-baseline, which I didn't yet
create.
Some work to build the documentation for real (possibly shielded by a
pseudo flavor) will follow.

Log message:
bump after default python version switch

Log message:
zap autoconf-N: part, since it's now default

Log message:
new depends

Log message:
more WANTLIB

Log message:
move gettext to new WANTLIB

Log message:
Remove USE_X11.

Log message:
USE_GROFF=Yes

Log message:
- upstream regenerated the tarball.
committing on behalf of kili@

Log message:
Bump revision after python's default change.

Log message:
Adjust WANTLIB and bump.
Silence post-extract a little bit.
Enable regression tests.

Log message:
Mark as BROKEN on hppa, SIGILL during build.

Log message:
Update to 2.12.3.

Log message:
Unbreak the build after the removal of ${LOCALBASE}/lib/X11/fonts/ghostscript.
No pkg bump necessary, since the ghostscript fonts are used during build time
only.

Log message:
Update to 2.12.2, following the guile update.
May still be broken a little bit; I'll fix any possible bugs
soon.

Log message:
WANTLIB changes after xcb addition and bump.

Log message:
CONFIGURE_ENV += PYTHON="${MODPY_BIN}" is inherited from the python module

Log message:
- nothing should have to run_depends on rarian anymore
- explicitely add build_depends on rarian where gnome-doc-utils is also a
build dependency as it does not itself run_depends on rarian anymore
This was the 2nd and hopefully last pass of rarian/scrollkeeper cleaning.
discussed with jasper@

Log message:
- first pass at cleaning rarian/scrollkeeper handling
remove rarian-sk-update from PLIST ; it is only a wrapper that does
noting: librarian takes care of everything now.
discussed with jasper@

Log message:
- switch to rarian instead of scrollkeeper
- regen PLIST
ok ajacoutot@

Log message:
- add missing scrollkeeper-update goo

Log message:
bump PKGNAME after python version switch

Log message:
Update to 2.10.33.

Log message:
Remove surrounding quotes in COMMENT/PERMIT_*/ERRORS

Log message:
Update to 2.10.25.

Log message:
Better COMMENTs. Noticed after a general mail from espie@.

Log message:
base64 checksums.

Log message:
Unbreak for xenocara: don't even run fc-cache, fix WANTLIB (+ expat z).
While here, remove a bogus patch also related to fc-cache that is
never invoked (target install-fc-cache).
ok, martynas@

Log message:
really depend on specified autoconf/automake version

Log message:
Fix MASTER_SITES. Found by and from Charles Longeau, thanks!

Log message:
Remove an unused variable.

Log message:
update to 2.8.8
new MULTI_PACKAGES
from kili@ with some corrections by me.

Log message:
USE_X11