[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-devel
Subject:    Re: Support for testing min and max versions of Guile. (issue 11303044)
From:       Julien Rioux <julien.rioux () gmail ! com>
Date:       2013-07-22 18:09:52
Message-ID: CAG4vuP0=pfS-iz8BjHZvXcgfuY2CAok7mg5YVixnVo1o=RbH0Q () mail ! gmail ! com
[Download RAW message or body]

On Mon, Jul 22, 2013 at 1:18 PM, Graham Percival
<graham@percival-music.ca>wrote:

> On Mon, Jul 22, 2013 at 02:03:31PM +0000, dak@gnu.org wrote:
> > As far as I know, 1.9 is the development series culminating in the
> > stable 2.0, so while 1.9 is not all too likely to be installed on
> > current systems, allowing/preferring it over 1.8 is not going to be
> > helpful.  I think the cutoff point should be at 1.9.
>
> Good point.
>
>
I'll make sure to make the change before committing.


> > Do we have an override option for those people who actually want to
> > develop towards 2.0 or are they supposed to edit the autoconf files?
>
> Don't we have a separate branch for guile-2.0?  If not, we should,
> and that branch can change the numbers to "guile 2.0 or higher".
> (or 2.x if we rely on any more recent guile features or bugfixe)
>

One overrides these auto settings in the usual way, setting
GUILE=/path/to/guile etc on the command line. And as you have seen, once we
are ready for guile 2, it's a one-line change in configure.ac

>> Should we document this somewhere?

I think the commit message, pointing to the relevant tracker issue and code
review, should be sufficient.

Cheers,
Julien

[Attachment #3 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, \
Jul 22, 2013 at 1:18 PM, Graham Percival <span dir="ltr">&lt;<a \
href="mailto:graham@percival-music.ca" \
target="_blank">graham@percival-music.ca</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div class="im">On Mon, Jul 22, 2013 at 02:03:31PM \
+0000, <a href="mailto:dak@gnu.org">dak@gnu.org</a> wrote:<br>

&gt; As far as I know, 1.9 is the development series culminating in the<br>
&gt; stable 2.0, so while 1.9 is not all too likely to be installed on<br>
&gt; current systems, allowing/preferring it over 1.8 is not going to be<br>
&gt; helpful.  I think the cutoff point should be at 1.9.<br>
<br>
</div>Good point.<br>
<div class="im"><br></div></blockquote><div><br></div><div>I&#39;ll make sure to make \
the change before committing.<br></div><div> </div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <div class="im">
&gt; Do we have an override option for those people who actually want to<br>
&gt; develop towards 2.0 or are they supposed to edit the autoconf files?<br>
<br>
</div>Don&#39;t we have a separate branch for guile-2.0?  If not, we should,<br>
and that branch can change the numbers to &quot;guile 2.0 or higher&quot;.<br>
(or 2.x if we rely on any more recent guile features or \
bugfixe)<br></blockquote><div><br></div><div>One overrides these auto settings in the \
usual way, setting GUILE=/path/to/guile etc on the command line. And as you have \
seen, once we are ready for guile 2, it&#39;s a one-line change in <a \
href="http://configure.ac">configure.ac</a><br> <br><pre name="cl-message-1">&gt;&gt; \
Should we document this somewhere?</pre>I think the commit message, pointing to the \
relevant tracker issue and code review, should be \
sufficient.<br><br></div><div>Cheers,<br>Julien<br> </div></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]