Op dinsdag 08-09-2009 om 02:42 uur [tijdzone +0200], schreef Reinhold
Am Dienstag, 8. September 2009 01:19:11 schrieb Graham Percival:
I can't figure out which piece of the build system does it.
TOPLEVEL_VERSION is an (auto)make variable, defined in aclocal.m4:
. $srcdir/VERSION
On Tue, Sep 08, 2009 at 09:36:22AM +0200, Jan Nieuwenhuizen wrote:
Guys! What happened to grep?
I had honestly completely forgotten that there was a make/ dir;
I'd been looking in stepmake/ and Documentation/.
And common sense...? this would mean that
* it's hardcoded until you run
Op dinsdag 08-09-2009 om 08:53 uur [tijdzone +0100], schreef Graham
Percival:
On Tue, Sep 08, 2009 at 09:36:22AM +0200, Jan Nieuwenhuizen wrote:
Guys! What happened to grep?
I had honestly completely forgotten that there was a make/ dir;
I'd been looking in stepmake/ and Documentation/.
On Tue, Sep 08, 2009 at 10:17:49AM +0200, Jan Nieuwenhuizen wrote:
Op dinsdag 08-09-2009 om 08:53 uur [tijdzone +0100], schreef Graham
Percival:
On Tue, Sep 08, 2009 at 09:36:22AM +0200, Jan Nieuwenhuizen wrote:
Guys! What happened to grep?
I had honestly completely forgotten that
Hi guys,
Le mardi 08 septembre 2009 à 10:13 +0100, Graham Percival a écrit :
I propose to extend /VERSION to include:
STABLE_VERSION
DEVEL_VERSION
- I'm asking if it's a good idea.
This would be yet another incarnation of caching data from another
branch in Git sources, so please no.
Le samedi 05 septembre 2009 à 00:43 +0100, Graham Percival a écrit :
3) we might be switching to SCons soon, so there's unfortunately
little interest in tracking down the above problems. As always,
patches appreciated if you're particularly curious about this
issue.
I won't support
On 8 Sep 2009, at 02:42, Joe Neeman wrote:
If you meant ghostscript in particular, then I guess we'll have to
stay with ghostscript 8.70 for now.
We don't link to ghostscript -- we merely call the command line
program
-- so the GPL doesn't apply.
I think that copyright only applies to
Le lundi 07 septembre 2009 à 16:42 -0700, Patrick McCarty a écrit :
The part that (I think) is relevant to LilyPond is below:
[...]
The licensing of the Free version of the core Ghostscript code has
been changed to GPLv3 or later. Previously, the core code was GPLv2
only.
John Mandereau wrote:
Le dimanche 06 septembre 2009 à 09:30 +0200, Joseph Wakeling a écrit :
I'm not sure how to interpret what's there -- presumably that only a
subset of the intended output has been written to collated-files.pdf?
As Graham pointed out, you didn't paste the relevant part of
John Mandereau wrote:
Even if any program in LilyPond linked with gs, we'd have no problem
since LilyPond is licensed under GPLv2+ (GPL v2 or later).
Please correct me if I'm wrong.
That was the point of the re-opening of discussion -- my query on that
very point in relation to the new
Le mardi 08 septembre 2009 à 12:30 +0200, Joseph Wakeling a écrit :
[century_schoolbook_l_serif_3.0673828125]Segmentation fault (core
dumped)
command failed: /home/myusername/code/lily/out/bin/lilypond
What is the snippet that causes a segmentation fault?
I note that texi2html is only 1.78
John Mandereau wrote:
Le mardi 08 septembre 2009 à 12:30 +0200, Joseph Wakeling a écrit :
[century_schoolbook_l_serif_3.0673828125]Segmentation fault (core
dumped)
command failed: /home/myusername/code/lily/out/bin/lilypond
What is the snippet that causes a segmentation fault?
It's trying
Op dinsdag 08-09-2009 om 12:34 uur [tijdzone +0200], schreef Joseph
Wakeling:
The
copyright file in my distro (Ubuntu) refers to GPLv2 or later
Which file are you referring to, and what does it say?
Jan.
--
Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond - The music typesetter
Avatar®:
Le mardi 08 septembre 2009 à 12:46 +0200, Joseph Wakeling a écrit :
It's trying to build BUILD-DIR/out/lybook-db/snippet-names--494188324.ly
whose content is:
I meant, what is the exact snippet that fails? Does it still fail if
you compile it with the trick described in HACKING and with EPS
Op dinsdag 08-09-2009 om 13:02 uur [tijdzone +0200], schreef Joseph
Wakeling:
Jan Nieuwenhuizen wrote:
Op dinsdag 08-09-2009 om 12:34 uur [tijdzone +0200], schreef Joseph
Wakeling:
The
copyright file in my distro (Ubuntu) refers to GPLv2 or later
Which file are you referring to,
Op dinsdag 08-09-2009 om 13:16 uur [tijdzone +0200], schreef Jan
Nieuwenhuizen:
Not only out-of-date, but also /wrong/. I just checked our sources,
a very early one and the one that was claimed to be packaged
git show release/{1.0.1,2.2.2}:{COPYING,main.cc}
git show
Jan Nieuwenhuizen wrote:
Op dinsdag 08-09-2009 om 13:16 uur [tijdzone +0200], schreef Jan
Nieuwenhuizen:
Not only out-of-date, but also /wrong/. I just checked our sources,
a very early one and the one that was claimed to be packaged
git show release/{1.0.1,2.2.2}:{COPYING,main.cc}
I wrote:
Second: Lilypond is part of the GNU project and GNU programs typically
have the 'or later' option, and indeed there is a perception that they
will upgrade to the latest GPL by default.
... see the general information on making a package part of the GNU project:
On Tue, Sep 8, 2009 at 6:51 AM, Hans Aberghab...@math.su.se wrote:
If you meant ghostscript in particular, then I guess we'll have to
stay with ghostscript 8.70 for now.
We don't link to ghostscript -- we merely call the command line program
-- so the GPL doesn't apply.
I think that
Hello all,
1. Can anyone explain the logic behind the decision to make
\smallCaps and \caps do the same thing?
2. Is there another [apparently undocumented] \uppercase command?
Thanks,
Kieren.
___
lilypond-devel mailing list
Hi Carl,
thanks for your review.
But the things they stand for are symbols elsewhere in the code, so I'd
prefer using symbols here.
Sure, but...
http://codereview.appspot.com/115065/diff/1001/1003#newcode232
Line 232: ((value-symbol (string-symbol (string-append (car value)
-default)))
I you
Op dinsdag 08-09-2009 om 11:51 uur [tijdzone +0200], schreef Hans Aberg:
On 8 Sep 2009, at 02:42, Joe Neeman wrote:
I think that copyright only applies to how it is redistributed
Almost, copyright is about copying.
So its GPL version will apply
No, it does not, as Joe pointed out.
Can you
On 8 Sep 2009, at 14:33, Han-Wen Nienhuys wrote:
I think that copyright only applies to how it is redistributed, and
not how
it is used. Mac OS X LilyPond has a gs in its distribution. So its
GPL
version will apply to that part when (re-)distribution. So you need
to make
sure that when you
On 8 Sep 2009, at 15:06, Jan Nieuwenhuizen wrote:
Can you please read the GNU GPL before spreading too much nonsense?
I have now looked through it, and found nothing of it. So you will
have to clarify.
Hans
___
lilypond-devel mailing list
Am Dienstag, 8. September 2009 16:19:43 schrieb Hans Aberg:
On 8 Sep 2009, at 15:06, Jan Nieuwenhuizen wrote:
On 8 Sep 2009, at 02:42, Joe Neeman wrote:
I think that copyright only applies to how it is redistributed
Almost, copyright is about copying.
Quote?
So its GPL version will
On 8 Sep 2009, at 15:06, Jan Nieuwenhuizen wrote:
On 8 Sep 2009, at 02:42, Joe Neeman wrote:
I think that copyright only applies to how it is redistributed
Almost, copyright is about copying.
Quote?
So its GPL version will apply
No, it does not, as Joe pointed out.
Can you please
Hi folks,
After a bit of private discussion with Jan and Graham, I've decided to
stop maintaining current build system (or rather the parts I used to
maintain), and we should switch to a build system that allows writing
build routines easier to maintain and understand. Jan proposed SCons
[0],
On 8 Sep 2009, at 16:51, Reinhold Kainhofer wrote:
Can you please read the GNU GPL before spreading too much nonsense?
It is not about the GPL, but the WIPO copyright treaty, and copyright
law. The GPL cannot override that.
gs is GPL v3+, so anything that links to it has to be compatible to
This works like the `bracket' markup command but makes parentheses
instead of brackets.
New public procedure `parenthesize-stencil' and subroutine
`make-parenthesis-stencil' in `scm/stencil.scm'.
Thanks to Carl Sorensen and Neil Puttock for their great advice and
criticism.
---
Hi Trevor,
I now think teaching the \new Voice method at the start gives a
better and sounder grounding.
I've always thought so...
Does this mean you don't need me to immediately rework how \\ voicifies?
Would that still be a good thing regardless of how the docs are written?
Cheers,
On Tue, Sep 08, 2009 at 11:50:09AM +0200, John Mandereau wrote:
Hi guys,
Le mardi 08 septembre 2009 à 10:13 +0100, Graham Percival a écrit :
I propose to extend /VERSION to include:
STABLE_VERSION
DEVEL_VERSION
- I'm asking if it's a good idea.
This would be yet another
Jan proposed SCons [0], and after having read SCons User Manual, I
think we could make good use of it. However, SCons has severe speed
issues, which Waf [1], one of his younger (and Python-based, just
like SCons) competitors, doesn't have -- see benchmarks [2] and [3].
Please have a look at
On Tue, Sep 08, 2009 at 08:25:24PM +0200, Werner LEMBERG wrote:
Jan proposed SCons [0], and after having read SCons User Manual, I
think we could make good use of it. However, SCons has severe speed
issues, which Waf [1], one of his younger (and Python-based, just
like SCons) competitors,
On Tue, Sep 08, 2009 at 06:13:34PM +0200, John Mandereau wrote:
If we decide to adopt this, my plan is to develop Waf scripts for what I
know best and sucks most in our current build system: the documentation
(including the future web site). Building the binary program would be
dealt with
For the record (as discussed in private email), I'm quite concerned
about waf's relative new-ness and occasional lack of development.
My preference would be to use a stable, widely used build system,
since any problems in the build system can cause a huge problem to
developers. [...]
BTW,
Hi all,
Let's say I want to create a new subclass of the Staff context called
MyStaff, and the only thing it does is override the InstrumentName
settings. Do I really have to include all the \consists from engraver-
init.ly? i.e., do I really have to use
\context {
\type
Le 8 sept. 09 à 14:43, Kieren MacMillan a écrit :
Hello all,
1. Can anyone explain the logic behind the decision to make
\smallCaps and \caps do the same thing?
\caps used to change the font shape to caps, which is available in eg
ccm, but not in CenturySchoolBook. So when the later was
Hi Nicolas,
\caps used to change the font shape to caps, which is available in eg
ccm, but not in CenturySchoolBook. So when the later was the default
font, \caps had no effect.
A hackish \smallCaps was developped, which change lower case
letters to
smaller upper case letters.
So at some
Le mardi 08 septembre 2009 à 19:41 +0100, Graham Percival a écrit :
While I feel incredibly guilty for speaking against any project
that includes a link to XKCD, I really do not think this is the
best project for us.
Neither do I.
- is it portable? (quote: there is no configure script, so
Kieren MacMillan wrote Tuesday, September 08, 2009 5:08 PM
Does this mean you don't need me to immediately rework how \\
voicifies?
I think I'll go ahead with the reordering anyway,
although it might take a while, as I have limited
time at present. So let's decouple the rewrite
of docs and
Le mardi 08 septembre 2009 à 21:12 +0200, Werner LEMBERG a écrit :
BTW, there is a `better make', written in Perl:
http://makepp.sourceforge.net/
According to this page, makepp `currently runs only on probably all
Linux/Unix-variants and Windows, as well as Ebcdic platforms BS2000
and
2009/9/6 Reinhold Kainhofer reinh...@kainhofer.com:
No conversion rule required. It's an internal property, so anyone messing with
them should be aware that it might break at any time.
The voice of reason, as always. :)
I've uploaded a few changes, since there was some quirky behaviour
with
Le mardi 08 septembre 2009 à 19:53 +0100, Graham Percival a écrit :
For the record (as discussed in private email), I'm quite
concerned about waf's relative new-ness and occasional lack of
development. My preference would be to use a stable, widely used
build system, since any problems in the
On 2009-09-08, at 15:25 , Kieren MacMillan wrote:
It would be so much easier to be able to force inheritance of
everything, e.g.
\context {
\name MyStaff
\from Staff
instrumentName = #MyStaff
shortInstrumentName = #My
}
Is there anything like this? (From what I've read and
44 matches
Mail list logo
