From: David Kastrup <dak@gnu.org>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: Documentation of reduce in guile manual
Date: Thu, 14 Apr 2011 12:23:21 +0200 [thread overview]
Message-ID: <87sjtl3zdy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m38vvdfctg.fsf@unquote.localdomain> (Andy Wingo's message of "Thu, 14 Apr 2011 10:37:47 +0200")
Andy Wingo <wingo@pobox.com> writes:
> On Thu 14 Apr 2011 10:18, David Kastrup <dak@gnu.org> writes:
>
>> Andy Wingo <wingo@pobox.com> writes:
>>
>>> On Tue 12 Apr 2011 14:00, David Kastrup <dak@gnu.org> writes:
>>>
>>>> In the guile manual (listed as
>>>> ii guile-1.6-doc
>>>
>>> For words that aren't ten years old, try Guile 2.0, which fixes this
>>> issue, among others.
>>
>> It is the version of guile with the API used in the very latest versions
>> of Debian and Ubuntu (to be released), so the "10 year old words" will
>> stick around for at least a year.
>
> I believe they also package guile-1.8-doc, which are merely 5 year old
> words.
Well, that explains some. It would appear that
a) docs are not installed by default, one has to install them manually
b) there is no metapackage guile-doc, so one has to specify versions
explicitly
c) once one installs guile-1.6-doc, dpkg is happy to keep it around even
when one upgrades guile to 1.8
d) deinstalling guile-1.6-doc after installing guile-1.8-doc*,
one needs to look for the file "guile-1.8" as info. guile.info no
longer is there, even after running dpkg-reconfigure on the
guile-1.8-doc* packages.
e) the documentation for reduce indeed is quite better.
--
David Kastrup
next prev parent reply other threads:[~2011-04-14 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 12:00 Documentation of reduce in guile manual David Kastrup
2011-04-14 8:00 ` Andy Wingo
2011-04-14 8:18 ` David Kastrup
2011-04-14 8:37 ` Andy Wingo
2011-04-14 10:23 ` David Kastrup [this message]
2011-04-14 14:26 ` Andy Wingo
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjtl3zdy.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.com \
/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.
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).