From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 15194@debbugs.gnu.org
Subject: bug#15194: hop FTBFS
Date: Tue, 27 Aug 2013 17:18:20 +0200 [thread overview]
Message-ID: <87haebgo1v.fsf@gnu.org> (raw)
In-Reply-To: <87k3j75glw.fsf@tines.lan> (Mark H. Weaver's message of "Tue, 27 Aug 2013 10:54:35 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> It turns out Hop & Bigloo have to be upgraded in lockstep. I believe
>> a new Hop version is around the corner, so I’m tempted to just wait
>> for that.
>>
>> WDYT?
>
> I think we should find a solution that doesn't lead to the 'hop' build
> being broken every time 'bigloo' is upgraded before 'hop'.
>
> An obvious solution would be to keep two versions of 'bigloo': the
> latest release, and the release that corresponds to the latest release
> of 'hop'. Hopefully these would be the same most of the time.
Yes, that sounds like a plan. And hopefully the “old” Bigloo would just
differ by its ‘version’ and ‘source’ fields, which is easily handled.
Would you like to propose a patch?
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-08-27 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 21:39 bug#15194: hop FTBFS Mark H Weaver
2013-08-27 8:27 ` Ludovic Courtès
2013-08-27 14:54 ` Mark H Weaver
2013-08-27 15:18 ` Ludovic Courtès [this message]
2013-08-30 1:35 ` Mark H Weaver
2013-08-30 12:19 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87haebgo1v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=15194@debbugs.gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).