Le mardi 26 juin 2012 à 08:06 +0100, Graham Percival a écrit :
> If you're going to rename stuff, I strongly suggest a bigger
> rename or you're asking for trouble. I suggest
> Documentation/lsr/ ? and Documentation/lsr/new/ ? and then the
> corresponding /build/ dirs will be created.
Regarding
On Mon, Jun 25, 2012 at 12:31:45PM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> To: "Phil Holmes"
> Cc: "Devel"
> Sent: Thursday, June 21, 2012 7:47 PM
> Subject: Re: LSR updates and translations
>
>
On Mon, Jun 25, 2012 at 12:50:15PM +0100, Phil Holmes wrote:
> I think the major challenge for me in changing the way the snippets
> are managed will be updating the various makefiles so that all the
> dependencies of the snippets are built from the new directory in
> /build rather than the old one
On 25/06/2012 1:53 PM, John Mandereau wrote:
Il giorno lun, 25/06/2012 alle 18.50 +0100, Phil Holmes ha scritto:
And John M could no doubt help. It's a question of how much time they have
to contribute.
If what we want to achieve is well enough specified, then I can offer to
go for it.
Cheers
Il giorno lun, 25/06/2012 alle 12.31 +0100, Phil Holmes ha scritto:
> Yes, that directory exists. Good point. perhaps the best name would be
> /build/Documentation/snippet-src?
What about $(top-build-dir)/Documentation/snippets/out? (read
$(top-build-dir) as "build/" if you prefer)
> The same
Il giorno lun, 25/06/2012 alle 18.50 +0100, Phil Holmes ha scritto:
> And John M could no doubt help. It's a question of how much time they have
> to contribute.
If what we want to achieve is well enough specified, then I can offer to
go for it.
Cheers,
John
___
- Original Message -
From: "Francisco Vila"
I think Julien Rioux is a good candidate for this.
And John M could no doubt help. It's a question of how much time they have
to contribute.
--
Phil Holmes
___
lilypond-devel mailing l
2012/6/25 Phil Holmes :
> I think the major challenge for me in changing the way the snippets are
> managed will be updating the various makefiles so that all the dependencies
> of the snippets are built from the new directory in /build rather than the
> old one in /Documents. If anyone with build
- Original Message -
From: "John Mandereau"
To: "Jean-Charles Malahieude"
Cc: "Phil Holmes" ; "Devel"
Sent: Thursday, June 21, 2012 10:35 AM
Subject: Re: LSR updates and translations
Il giorno mer, 20/06/2012 alle 19.40 +0200, Jean-Charle
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Devel"
Sent: Thursday, June 21, 2012 7:47 PM
Subject: Re: LSR updates and translations
On Wed, Jun 20, 2012 at 10:50:42AM +0100, Phil Holmes wrote:
I'd like to propose a pretty
2012/6/21 Graham Percival :
> [2] let me give a huge disclaimer here: the way that we track
> translations, or translation update notifications, or whatever,
> could probably be improved.
It can be improved because it is broken.
> I have no clue what those git
> committishes are doing; at first
On Wed, Jun 20, 2012 at 10:50:42AM +0100, Phil Holmes wrote:
> I'd like to propose a pretty radical change to this process. I
> propose that /Documentation/snippets/ is a straight copy of a recent
> LSR tarball.
I assume you mean the doc-related LSR tarball, not the full LSR
tarball.
> It's the
Il giorno mer, 20/06/2012 alle 19.40 +0200, Jean-Charles Malahieude ha
scritto:
> Just a nitpick: since info files are built during the "make" phase, it
> might be more judicious to attach "make snippets" to this phase.
Oh, that's right, I forgot about those Info files without images; in
make lan
2012/6/20 Phil Holmes :
> My idea would be that, using the new system, changed snippets would look
> exactly like changed documentation files. If I modify, say,
> /Documentation/notation/ancient.itely, how do the translators pick up that
> this has been changed?
Sorry, this is moving very fast. I
Le 20/06/2012 11:50, Phil Holmes disait :
I'd like to propose a pretty radical change to this process. I propose
that /Documentation/snippets/ is a straight copy of a recent LSR
tarball. It's the task of the LSR meister to keep this up to date. We
have a new directory: build/Documentation/sni
2012/6/20 Phil Holmes :
> - Original Message - From: "Francisco Vila"
> To: "Phil Holmes"
>
>
>> Good, I like it in principle, but how will be changes being tracked
>> using SHA IDs?
>>
>> Currently, translations have a SHA ID which is that of the snippet it
>> is a translation of. Any ch
- Original Message -
From:
To: "Phil Holmes"
Cc: "Devel"
Sent: Wednesday, June 20, 2012 11:38 AM
Subject: Re: LSR updates and translations
On 20 juin 2012, at 12:29, Phil Holmes wrote:
- Original Message - From: "Francisco Vila"
To: "
Hi Phil,
Il giorno mer, 20/06/2012 alle 10.50 +0100, Phil Holmes ha scritto:
> I'd like to propose a pretty radical change to this process. I propose that
> /Documentation/snippets/ is a straight copy of a recent LSR tarball. It's
> the task of the LSR meister to keep this up to date. We have
On 20 juin 2012, at 12:29, Phil Holmes wrote:
> - Original Message - From: "Francisco Vila"
> To: "Phil Holmes"
>
>> Good, I like it in principle, but how will be changes being tracked
>> using SHA IDs?
>>
>> Currently, translations have a SHA ID which is that of the snippet it
>> is a
Hi Francisco,
Il giorno mer, 20/06/2012 alle 12.04 +0200, Francisco Vila ha scritto:
> Good, I like it in principle, but how will be changes being tracked
> using SHA IDs?
>
> Currently, translations have a SHA ID which is that of the snippet it
> is a translation of. Any change to the original sn
- Original Message -
From: "Francisco Vila"
To: "Phil Holmes"
Good, I like it in principle, but how will be changes being tracked
using SHA IDs?
Currently, translations have a SHA ID which is that of the snippet it
is a translation of. Any change to the original snippet is done in a
2012/6/20 Phil Holmes :
> I'd like to propose a pretty radical change to this process. I propose that
> /Documentation/snippets/ is a straight copy of a recent LSR tarball. It's
> the task of the LSR meister to keep this up to date. We have a new
> directory: build/Documentation/snippets. This
I've been having a think about how LSR snippets and the translations are
managed in our build system. At present, I understand the system works as
follows.
We would start with a downloaded tarball of snippets, and run makelsr.py
using that as an argument. This takes the snippets from the tar
23 matches
Mail list logo
