kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
197964 commits 166 branches 0 tags 1.5 GiB
Commit graph

88 commits

Author SHA1 Message Date
wiz
a96f4900ac Recursive bump for png-1.6. 2013-02-16 11:18:58 +00:00
wiz
628bd7d7fb Update to 2.16.2. Comment patches. 
Fixes and changes after 2.16.0
==============================

2.16.1
     Please refer to the bug tracker for issues fixed in 2.16.1
     (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1).

New features in 2.16 since 2.14
===============================

   * Support for cross-staff stems on chords, using `crossStaff' and
     the `Span_stem_engraver'.  This calculates the length of
     cross-staff stems automatically.

   * The syntax of words (character sequences recognized without
     enclosing quotes) and commands (now always a backslash `\'
     followed by a word) has been unified across all modes: it now
     consists of alphabetic characters, possibly enclosing isolated
     dashes `-' and underlines `_'.

     As one consequence, using unquoted text scripts like (literally!)
          { c-script c\f_script }
     will now tend to result in invalid music.  Omitting quote marks
     for arbitrary text rather than keywords has never been good
     practice or even documented, and it is unlikely to have seen
     significant use.

     Staying with established conventions (like not using dashes or
     underlines for command names intended to be used inside of music)
     remains advisable.  The reason for this change is more robust
     recognition of LilyPond's lexical units for LilyPond itself as
     well as external tools interpreting its syntax.

   * Support for Kievan square notation:

          \new KievanVoice {
            \cadenzaOn
            c d e f g a bes
            \bar "kievan"
          }

   * Augmentation dots now avoid the other voice in two-voice polyphony
     so that users can move the `Dot_column_engraver' to set dots
     independently for each `Voice'.

   * A Scheme function to adjust the control points of curves such as
     slurs and ties, developed by several users, is now included in
     LilyPond.

          g8->( bes,-.) d4
          \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0))
          g8->( bes,!-.) d4

   * Use of `\tempo' specifications in `\midi' blocks (removed in
     2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has
     seen a revival: now any kind of property-setting music is turned
     into context definitions within output specifications, allowing for
     declarations like
     \layout { \accidentalStyle modern }
     \midi { \tempo 4. = 66 }

   * The LilyPond G clef has been redesigned - upper loop is now more
     balanced, bottom crook sticks out less and the "spine" (main
     vertical line) is more evenly curved. The old and new versions can
     be compared by looking at the documentation: old version
     (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs),
     new version
     (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs).

   * Lilypond's stencil commands have been simplified to allow for less
     code duplication and better height approximations of graphical
     objects.  The following stencil commands have been eliminated:
        * `beam'

        * `bezier-sandwich'

        * `bracket'

        * `dashed-slur'

        * `dot'

        * `oval'

        * `repeat-slash'

        * `zigzag-line'

   * Flags are now treated as separate objects rather than as stem
     parts.

   * Two alternative methods for bar numbering can be set, especially
     for when using repeated music;

   * The following is a fundamental change in LilyPond's music
     representation: Rhythmic events like `LyricEvent' and `NoteEvent'
     are no longer wrapped in `EventChord' unless they have been
     actually entered as part of a chord in the input.  If you
     manipulate music expressions in Scheme, the new behavior may
     require changes in your code.  Calling the music function
     `\eventChords' or the Scheme function `event-chord-wrap!'
     converts to the old representation; using one of those might be
     easiest for keeping legacy code operative.

     The following three items are consequences of this change.

   * The repetitive chord entry aid `q' has been reimplemented.
     Repeated chords are now replaced right before interpreting a music
     expression.  In case the user wants to retain some events of the
     original chord, he can run the repeat chord replacement function
     `\chordRepeats' manually.

   * String numbers and right hand fingerings on single notes now appear
     without having to be written inside of chord brackets.

   * Music functions now work the same when used inside or outside of
     chords, including all the possibilities of argument parsing.
     Music variables can be used inside of chords: a construct like

          tonic=fis'
          { <\tonic \transpose c g \tonic> }

     now works as expected.  One can use `#{...#}' for constructing
     chord constituents.  `\tweak' now works on single notes without
     needing to wrap them in a chord.  Using it on command events and
     lyrics is now possible, but not likely to give results yet.

   * `\tweak' now takes an optional layout object specification.  It can
     be used for tweaking layout objects that are only indirectly
     caused by the tweaked event, like accidentals, stems, and flags:

          <\tweak Accidental #'color #red   cis4
           \tweak Accidental #'color #green es
                                            g>

   * Scheme expressions inside of embedded Lilypond (`#{...#}') are now
     executed in lexical closure of the surrounding Scheme code.  `$'
     is no longer special in embedded Lilypond.  It can be used
     unconditionally in Lilypond code for immediate evaluation of Scheme
     expressions, similar to how `ly:export' could previously be used.
     `ly:export' has been removed.  As a consequence, `#' is now free
     to delay evaluation of its argument until the parser actually
     reduces the containing expression, greatly reducing the potential
     for premature evaluation.  There are also `splicing' operators `$@'
     and `#@' for interpreting the members of a list individually.

   * To reduce the necessity for using `$', Scheme expressions written
     with `#' are interpreted as music inside of music lists, and as
     markups or markup lists inside of markups.

   * Support for jazz-like chords has been improved: Lydian and altered
     chords are recognised; separators between chord modifiers are now
     treated independently of separators between "slash" chords and
     their bass notes (and by default, slashes are now only used for
     the latter type of separator); additional pitches are no longer
     prefixed with "add" by default; and the "m" in minor chords can be
     customized.  *note Customizing chord names:
     (lilypond-notation)Customizing chord names. for more information.

   * The `\markuplines' command has been renamed to `\markuplist' for a
     better match with its semantics and general Lilypond nomenclature.

   * The interface for specifying string tunings in tablature has been
     simplified considerably and employs the scheme function
     `\stringTuning' for most purposes.

   * Beams can now have their slopes preserved over line breaks.

     To do this, several callback functions are now deprecated.
        * `ly:beam::calc-least-squares-positions'

        * `ly:beam::slope-damping'

        * `ly:beam::shift-region-to-valid'
     Furthermore, `ly:beam::quanting' now takes an additional argument
     to help calculations over line breaks.  All of these functions are
     now automatically called when setting the `positions' parameter.

   * In function arguments music, markups and Scheme expressions (as
     well as several other syntactic entities) have become mostly
     interchangeable and are told apart only by evaluating the
     respective predicate.  In several cases, the predicate is
     consulted by the parser, like when deciding whether to interpret
     `-3' as a number or a fingering event.

   * Music functions (and their close relatives) can now be defined with
     optional arguments.

   * For defining commands executed only for their side-effects,
     `define-void-function' is now available.

   * There is a new `define-event-function' command in analogy to
     `define-music-function' that can be used for defining music
     functions acting as post events without requiring a direction
     specifier (`-', `^', or `_') placed before them.

          dyn=#(define-event-function (parser location arg) (markup?)
                   (make-dynamic-script arg))
          \relative c' { c\dyn pfsss }

   * A list of ASCII aliases for special characters can be included.

          \paper {
            #(include-special-characters)
          }
          \markup "&bull; &dagger; &copyright; &OE; &ss; &para;"

   * There is a new `define-scheme-function' command in analogy to
     `define-music-function' that can be used to define functions
     evaluating to Scheme expressions while accepting arguments in
     Lilypond syntax.

   * The construct `#{ ... #}' can now be used not just for
     constructing sequential music lists, but also for pitches
     (distinguished from single note events by the absence of a
     duration or other information that can't be part of a pitch),
     single music events, void music expressions, post events, markups
     (mostly freeing users from having to use the `markup' macro),
     markup lists, number expressions, context definitions and
     modifications, and a few other things.  If it encloses nothing or
     only a single music event, it no longer returns a sequential music
     list but rather a void music expression or just the music event
     itself, respectively.

   * Pitches can be used on the right side of assignments.  They are
     distinguished from single note events by the absence of a duration
     or other information that can't be part of a pitch.

   * New command-line option `--loglevel=LEVEL' to control how much
     output LilyPond creates. Possible values are ERROR, WARN,
     BASIC_PROGRESS, PROGRESS, DEBUG.

   * `\once \set' now correctly resets the property value to the
     previous value.

   * The alignment of dynamic spanners (hairpins, text crescendo, etc.)
     is now automatically broken if a different direction is explicitly
     given.

   * Appoggiaturas and acciaccaturas now also work inside a slur, not
     only inside a phrasing slur. Also, a function `\slashedGrace' was
     added that does not use a slur from the acciaccatura note.

   * To suppress the line on a crescendo text spanner (and other
     similar spanners), LilyPond now fully supports the `#'style =
     #'none' property.

   * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz!

   * Glissandi can now span multiple lines.
 2013-01-25 11:32:07 +00:00
marino
cba0cdaca6 print/lilypond: Fix redefinition of Moment S 
This problem, detected by gcc 4.6+, was fixed upstream a year ago.
Bring that patch in to fix the build.
 2012-12-15 10:01:20 +00:00
adam
ed93f0ca47 Revbump after updating graphics/pango 2012-10-08 23:00:34 +00:00
asau
e613b3f0ef Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days. 2012-10-08 13:45:34 +00:00
wiz
3184463075 Bump all packages that use perl, or depend on a p5-* package, or 
are called p5-*.

I hope that's all of them.
 2012-10-03 21:53:53 +00:00
tron
78f9c75877 Mass recursive bump after the dependence fix of the "cairo" package 
requested by Thomas Klausner.
 2012-10-02 17:10:28 +00:00
obache
8ace00dcd8 recursive bump from libffi shlib major bump 
(additionaly, reset PKGREVISION of qt4-* sub packages from base qt4 update)
 2012-09-15 10:03:29 +00:00
adam
e7608643ab Revbump after updating graphics/cairo 2012-09-07 19:16:05 +00:00
obache
34a560cbb0 Bump PKGREVISION from default python to 2.7. 2012-03-15 11:53:20 +00:00
minskim
8a5f3c5b66 Add missing build-time dependencies to lilypond. 2012-03-07 15:56:32 +00:00
minskim
0891e856b5 Reduce lilypond's dependencies on TeX. 2012-03-07 15:27:30 +00:00
wiz
e64308b04b Recursive bump for pcre-8.30* (shlib major change) 2012-03-03 00:11:51 +00:00
wiz
5fb1e22076 Revbump for 
a) tiff update to 4.0 (shlib major change)
b) glib2 update 2.30.2 (adds libffi dependency to buildlink3.mk)

Enjoy.
 2012-02-06 12:40:37 +00:00
marino
b0673c6c44 print/lilypond: Fix copy/paste error on previous commit 2011-12-06 19:05:35 +00:00
marino
30a1cd50bb print/lilypond: Fix for DragonFly 
DragonFly needs devel/flex rather than USE_TOOLS+= lex in order to
build lilypond
 2011-12-06 01:23:58 +00:00
sbd
94b37b4e43 Recursive bump for graphics/freetype2 buildlink addition. 2011-11-01 06:00:33 +00:00
ryoon
95a7b77e35 Update to 2.14.2 
* Update MASTER_SITES.

Changelog:
* New scripts introduced.
* MIDI input and output are improved.
* Some notation improvements.
* Some new signs are introduced.
* Unicode Bidirectional Algorithm is fully supported.
* and so on. see NEWS.txt.
 2011-07-31 09:12:46 +00:00
obache
0e2c97799a recursive bump from gettext-lib shlib bump. 2011-04-22 13:41:54 +00:00
ryoon
d489a65c92 Add dependency to texi2html, fontforge, and t1utils. 2011-03-09 11:05:12 +00:00
ryoon
05cfca4dc8 Set LICENSE. 2011-03-08 15:59:04 +00:00
ryoon
51ce9a9df6 Fix PR pkg/44693 
* Update HOMEPAGE.
* Remove dependency to ec-fonts-mftraced and mftrace.
* Works fine with python26, delete PYTHON_VERSIONS_ACCEPTED.
* Bump PKGREVISION.
 2011-03-08 15:55:46 +00:00
wiz
2f4126dc58 png shlib name changed for png>=1.5.0, so bump PKGREVISIONs. 2011-01-13 13:36:05 +00:00
drochner
62dce76480 -catch up with the ghostscript font changes a while ago 
-update to 2.12.3
 changes:
 -MacOSX GUI fixes
 -bugfixes
 2010-12-01 19:39:29 +00:00
wiz
2c6e8e30b0 Bump dependency on pixman to 0.18.4 because cairo-1.10 needs that 
version, and bump all depends.

Per discussion on pkgsrc-changes.
 2010-09-14 11:00:44 +00:00
wiz
92e0cb52cb Bump PKGREVISION for libpng shlib name change. 
Also add some patches to remove use of deprecated symbols and fix other
problems when looking for or compiling against libpng-1.4.x.
 2010-06-13 22:43:46 +00:00
asau
9d172bbac7 Recursive revision bump for GMP update. 2010-03-24 19:43:21 +00:00
joerg
a0e6713ee7 Recursive bump for libltdl 2009-12-15 21:54:17 +00:00
hasso
d70c9304f9 Update to 2.12.2. The list of upstream changes is too massive to put it 
here (almost two years of development).

http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list
of new features.
 2009-06-03 19:52:33 +00:00
wiz
f4e9595f26 Recursive ABI depends update and PKGREVISION bump for readline-6.0 shlib 
major change.

Reported by Robert Elz in PR 41345.
 2009-05-20 00:58:05 +00:00
wiz
78b7af7df5 Use mk/omf-scrollkeeper.mk instead of textproc/rarian/omf.mk. 2009-03-08 15:56:43 +00:00
joerg
3c645bb7fc Switch to Python 2.5 as default. Bump revision of all packages that have 
changed runtime dependencies now.
 2009-02-09 22:56:21 +00:00
wiz
55fa90af5f Move scrollkeeper/omf.mk to rarian/omf.mk. 
scrollkeeper is nowadays included in rarian, so the omf.mk file should
be there as well.
Adapt all references.
 2009-01-04 18:00:58 +00:00
joerg
f605fec2db Mark as destdir ready. 2008-07-14 12:55:56 +00:00
wiz
3a9858ff0e Fix a few problems: 
. Fontforge version comparison in configure script is broken, because
  the numbers get too big for test(1). Comment it out, we know the
  pkgsrc version is new enough.
. Do not install any emacs lisp files. Should be a separate package.
. Give path to Century New Schoolbook L fonts to configure script directly.
  There seems to be some problem with fc-match in a sandbox (to be
  investigated).

Bump PKGREVISION for PLIST change.

Changes created in cooperation with dillo@ and schmonz@ at pkgsrcCon 2008.
 2008-06-18 20:29:32 +00:00
wiz
87cc1b5550 Needs pkg-config, and does not like python<2.4. 
XXX: still does not build for me because it does not accept fontforge.
 2008-06-10 08:05:21 +00:00
sborrill
399bb76d8d Update to 2.10.33. 
Changes are too numerous to mention.

N.B. I've removed the dependency on emacs, it was only used to create the
folder to install a single folder in and worse still, PLIST used
EMACS_LISPPREFIX but this wasn't used by Lilypond.
 2008-05-14 20:25:15 +00:00
obache
289a48ce89 Master site's layout has been changed. 2006-12-31 16:39:34 +00:00
obache
f8132f56ec Update lilypond to 2.4.6. 
This release backports the tieWaitForNote feature and has support for tetex-3.0
and some fixes.
 2006-12-29 07:11:55 +00:00
joerg
e245fc63f9 Needs msgfmt. XXX Where does inimf come from? 2006-09-11 08:33:11 +00:00
obache
e896edb7fe Rename variable MAKEFILE to MAKE_FILE. 2006-09-09 02:41:53 +00:00
rillig
d75c9e37ba Lilypond needs Perl to build. 2006-08-31 18:11:31 +00:00
minskim
49c97b520c USE_TOOLS+=flex 2006-08-08 19:14:39 +00:00
jlam
292727e131 List the info files directly in the PLIST and honor PKG{INFO,MAN}DIR. 2006-04-06 18:18:15 +00:00
jlam
39a303999a USE_TOOLS+=bison instead of direct BUILD_DEPENDS on bison. 2006-04-06 16:27:30 +00:00
reed
5abef9be14 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-04-06 06:21:32 +00:00
jlam
11993b86ed Bump PKGREVISION for all packages that had broken INSTALL/DEINSTALL 
scripts prior to revision 1.43 of bsd.pkginstall.mk.
 2006-03-21 06:00:43 +00:00
jlam
6e0c050321 * Teach the tools framework how to supply the pkgsrc version of 
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.
 2006-03-05 16:27:22 +00:00
jlam
9c8b5ede43 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-03-04 21:28:51 +00:00
joerg
5911def816 Recursive revision bump / recommended bump for gettext ABI change. 2006-02-05 23:08:03 +00:00