I don't see why the distros should not provide libguile 1 as well as
libguile 2. They are clearly different enough to warrant it.
On 5 Jun 2016 6:06 p.m., "Karl Hegbloom" <karl.hegbl...@gmail.com> wrote:

> Work was begun but not completed. I want to help complete it but have
> other obligations right now so can't spend full time on it. I'm also not
> necessarily the most qualified in terms of knowledge and experience,  but
> will try. The work that was done is on a branch in my git clone,  on
> github. It was a long time ago.
>
> I think that we should go straight to Guile 2.2.
>
> On Sun, Jun 5, 2016, 02:45 Ingolf Schaefer <ingolf.schae...@gmail.com>
> wrote:
>
>> Am Samstag, 4. Juni 2016, 10:26:34 schrieb kamaraju kusumanchi:
>> > I see that my name is mentioned in the maintainers of Debian package
>> > of texmacs - http://www.texmacs.org/tmweb/download/linux.en.html#debian
>> > . Could you please remove it? I stopped maintaining it a while ago. In
>> > fact, Texmacs is removed from Debian unstable due to dependency on
>> > guile-1.8 (Debian has moved to guile-2.0) and lack of maintainer
>> > [1],[2].
>> >
>> >
>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797833
>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825252
>> >
>> > thanks
>> > raju
>> Hi,
>>
>> I can confirm that a similar discussion is happening in Mageia community.
>> I'm
>> afraid that this will come for other Linux distributions as well in
>> future.
>>
>> Is there any progress on a port to a recent Guile or another recent scheme
>> dialect?
>>
>> Yours,
>>
>> Ingolf
>>
>> _______________________________________________
>> Texmacs-dev mailing list
>> Texmacs-dev@gnu.org
>> https://lists.gnu.org/mailman/listinfo/texmacs-dev
>>
>
> _______________________________________________
> Texmacs-dev mailing list
> Texmacs-dev@gnu.org
> https://lists.gnu.org/mailman/listinfo/texmacs-dev
>
>
_______________________________________________
Texmacs-dev mailing list
Texmacs-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/texmacs-dev

Reply via email to