[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LSR update policies, and WTM is input/new/revised/ ?
From: |
Graham Percival |
Subject: |
Re: LSR update policies, and WTM is input/new/revised/ ? |
Date: |
Sun, 7 Jun 2009 11:54:24 -0700 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Sat, Jun 06, 2009 at 06:00:23PM -0500, Jonathan Kulp wrote:
> Graham Percival wrote:
>> ok. IMO, osx users should set up a "lilypond" shell script, as
>> suggested in AU 2.something. Then you wouldn't need that special
>> path-to-binary thing. But adding this as-is certainly can't hurt
>> the next person doing the update, so that's fine.
>
> Yeah, I almost took the OSX PATH out. I used to put it in all of my lily
> shell scripts before I figured out that it's better to set things up as
> described in AU. Since you lean that direction I wouldn't mind removing
> it. Do you want me to make a patch or would you rather do it yourself?
I did it, but now I'm wondering how the script worked at all --
doesn't the lsr tarball put things in separate dirs? Oh wait;
maybe the snippets-all has everything in one dir. Ok, never mind.
Cheers,
- Graham
- LSR update policies, and WTM is input/new/revised/ ?, Graham Percival, 2009/06/04
- Re: LSR update policies, and WTM is input/new/revised/ ?, Jonathan Kulp, 2009/06/04
- Re: LSR update policies, and WTM is input/new/revised/ ?, Graham Percival, 2009/06/05
- Re: LSR update policies, and WTM is input/new/revised/ ?, Jonathan Kulp, 2009/06/06
- Re: LSR update policies, and WTM is input/new/revised/ ?, Graham Percival, 2009/06/06
- Re: LSR update policies, and WTM is input/new/revised/ ?, Jonathan Kulp, 2009/06/06
- Re: LSR update policies, and WTM is input/new/revised/ ?,
Graham Percival <=
- Re: LSR update policies, and WTM is input/new/revised/ ?, Jonathan Kulp, 2009/06/07