On Fri, Oct 22, 2010 at 10:21:58PM +0200, Matthias Kilian wrote:
> On Tue, Oct 19, 2010 at 12:07:29AM +0100, Graham Percival wrote:
> > Anything that's used to build the website (as opposed to the html
> > version of the docs) cannot rely on configure. This affects
> > scripts/build/ create-*.py w
On Tue, Oct 19, 2010 at 12:07:29AM +0100, Graham Percival wrote:
> >> python/ yes, since it's not something that people call manually.
> >> But stuff in scripts/build/ shouldn't have @PYTHON@, otherwise
> >> it'll bork if you call it manually.
> >
> > But are those scripts supposed to be used witho
On Tue, Oct 19, 2010 at 8:02 AM, John Mandereau
wrote:
> Il giorno lun, 18/10/2010 alle 09.20 -0700, Patrick McCarty ha scritto:
>> On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
>> wrote:
>> > I don't understand the issue; can't you just set PYTHON=python2 when
>> > calling configure, and in ca
Il giorno lun, 18/10/2010 alle 09.20 -0700, Patrick McCarty ha scritto:
> On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
> wrote:
> > I don't understand the issue; can't you just set PYTHON=python2 when
> > calling configure, and in case you need some scripts in auxiliar call
> > them by prependi
(unlurking, i didn't spend much time on lilypond recently)
On Mon, Oct 18, 2010 at 01:59:15AM +0100, Graham Percival wrote:
> > --) Two scripts still have "/usr/bin/python" lines
> > (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
> > Those should be changed to "@PYTHON@", rig
On Mon, Oct 18, 2010 at 11:57 PM, Matthias Kilian
wrote:
> (unlurking, i didn't spend much time on lilypond recently)
>
>> python/ yes, since it's not something that people call manually.
>> But stuff in scripts/build/ shouldn't have @PYTHON@, otherwise
>> it'll bork if you call it manually.
>
> B
On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
wrote:
> Il giorno lun, 18/10/2010 alle 09.02 -0700, Patrick McCarty ha scritto:
>> Yes, but unfortunately, LilyPond needs special sed treatment, since
>> many substitutions are made *after* configure time. I will need to
>> file a bug report...
>>
Il giorno lun, 18/10/2010 alle 09.02 -0700, Patrick McCarty ha scritto:
> Yes, but unfortunately, LilyPond needs special sed treatment, since
> many substitutions are made *after* configure time. I will need to
> file a bug report...
>
> Specifically, I am looking for a way to make life easier wh
On Sun, Oct 17, 2010 at 5:59 PM, Graham Percival
wrote:
> On Sun, Oct 17, 2010 at 05:38:20PM -0700, Patrick McCarty wrote:
>> --) Two scripts still have "/usr/bin/python" lines
>> (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
>> Those should be changed to "@PYTHON@", right?
On Sun, Oct 17, 2010 at 11:19 PM, Mark Polesky wrote:
> Patrick McCarty wrote:
>> Huh. I've been following the Arch Linux development list
>> for a while, but it didn't occur to me that they were
>> doing something radically different than the recommended
>> policy.
>>
>> This is the procedure th
On Mon, Oct 18, 2010 at 2:50 AM, Valentin Villenave
wrote:
> On Mon, Oct 18, 2010 at 2:38 AM, Patrick McCarty wrote:
>> Arch Linux will be migrating to Python 3 very soon, and I'm trying to
>> figure out what to do with regard to LilyPond's build system. I don't
>> know if Arch Linux is the firs
On Mon, Oct 18, 2010 at 2:38 AM, Patrick McCarty wrote:
> Arch Linux will be migrating to Python 3 very soon, and I'm trying to
> figure out what to do with regard to LilyPond's build system. I don't
> know if Arch Linux is the first distribution upgrading to Python 3,
> but this migration will b
Patrick McCarty wrote:
> Huh. I've been following the Arch Linux development list
> for a while, but it didn't occur to me that they were
> doing something radically different than the recommended
> policy.
>
> This is the procedure they are following, and I think they
> are nearly finished with t
On Sun, Oct 17, 2010 at 8:30 PM, Benjamin Peterson wrote:
> Patrick McCarty gmail.com> writes:
>>
>> Arch Linux will be migrating to Python 3 very soon,
>
> What does this mean? "$ python" will give Python 3?
Yes.
> If so, that's no good. "python3" is supposed to be the name of the Python 3
> e
Benjamin Peterson python.org> writes:
> time in memoriam.
Hmm, that is a curious think-o. I meant "time immemorial" of course.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Patrick McCarty gmail.com> writes:
>
> Hello,
>
> Arch Linux will be migrating to Python 3 very soon,
What does this mean? "$ python" will give Python 3?
If so, that's no good. "python3" is supposed to be the name of the Python 3
executable for time in memoriam.
>
> The distribution-wide po
On Sun, Oct 17, 2010 at 05:38:20PM -0700, Patrick McCarty wrote:
> --) Two scripts still have "/usr/bin/python" lines
> (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
> Those should be changed to "@PYTHON@", right?
python/ yes, since it's not something that people call manual
Hello,
Arch Linux will be migrating to Python 3 very soon, and I'm trying to
figure out what to do with regard to LilyPond's build system. I don't
know if Arch Linux is the first distribution upgrading to Python 3,
but this migration will be happening any day now.
The distribution-wide policy is
18 matches
Mail list logo
