[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guile 3 migration plan
Re: Guile 3 migration plan
Thu, 16 Jan 2020 18:23:50 +0100
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
Efraim Flashner <address@hidden> skribis:
> On Thu, Jan 16, 2020 at 11:08:15AM +0100, Ludovic Courtès wrote:
>> Hello Guix!
>> Today is Guile 3 day, a day to celebrate, woohoo! \o/
>> How will Guix migrate to Guile 3? That’s a threefold process:
>> 1. We must first migrate packages. I propose to rename “guile-next”
>> to “guile” today, such that “guix install guile” will now install
>> Guile 3 (no mass rebuild involved: the “default” Guile remains
>> The downside is that if you run “guix install guile guile-json”,
>> you’ll get Guile 3 with Guile-JSON for 2.2; instead, you have to
>> explicitly select “guile3.0-json”.
> I feel like these should move together. Imagine if we had python
> libraries that only worked with python2 but called them python-foo
> anyway. Having consistent naming between the packages is important.
Note that it means that a number of “guile-” packages (those that do not
work yet with Guile 3) will disappear or be temporarily superseded by a
“guile2.2-” package, which again will not work with Guile 3.
So it’s not a great solution either; people may still have to explicitly
select guile@2 or something.
Now, whatever we choose, we can add an entry to ‘etc/news.scm’ to make
the transition smoother.
>> I propose renaming all the “guile3.0-” packages to “guile-”, and
>> all the “guile-” packages to “guile2.2-” as a second step, which
>> will address this issue. This could be done within a few days or
> It seems to me we could switch the guile packages to guile3.0 and leave
> guix at guile2.2. In any case, we should create a guix-with-guile3
> package to encourage people to try to fix bugs and try it out.
>> 2. We must be able to run Guix itself on Guile 3. This is already
>> possible if you add “3.0” to the ‘GUILE_PKG’ invocation in
>> ‘configure.ac’, but there are still a few test failures that I’ve
>> been working on. Almost all of them relate to the use of ‘@@’ and
>> ‘mock’, which do not work with Guile 3 “declarative modules”.
>> In many cases, it’s an opportunity to clean up our tests; see for
>> example 4aea90b1876179aab8d603a42533a6bdf97ccd3c and the preceding
>> commit. It should be possible to be done real soon!
> I'm going to miss '@@'
It’s still there, it just doesn’t give you what you want in some cases.
Anyhow, happy Guile 3 day! :-)
- Guile 3 migration plan, Ludovic Courtès, 2020/01/16
- Re: Guile 3 migration plan, zimoun, 2020/01/16
- Re: Guile 3 migration plan, Efraim Flashner, 2020/01/16
- Re: Guile 3 migration plan,
Ludovic Courtès <=
- Re: Guile 3 migration plan, Vagrant Cascadian, 2020/01/16
- Re: Guile 3 migration plan, Ludovic Courtès, 2020/01/17
- Re: Guile 3 migration plan, Ludovic Courtès, 2020/01/19
- Re: Guile 3 migration plan, Ludovic Courtès, 2020/01/20
- Re: Guile 3 migration plan, Ludovic Courtès, 2020/01/23
- Re: Guile 3 migration plan, Ricardo Wurmus, 2020/01/23
- Re: Guile 3 migration plan, Ludovic Courtès, 2020/01/24
- Re: Guile 3 migration plan, Ludovic Courtès, 2020/01/25
- Re: Guile 3 migration plan, Ricardo Wurmus, 2020/01/25