Bug 76693
Summary: | Obsolete and badly documented library of scheme code | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michal Jaegermann <michal> |
Component: | umb-scheme | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-10-24 23:34:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2002-10-24 23:33:57 UTC
I've updated the slib package to the latest version. I'll think about packaging it separately, but it doesn't make a lot of sense, because slib alone without umb-scheme doesn't really make a lot of sense, does it? :-) But i might build the documentation in it and put that somewhere sane so that it can be actually used. Will do that sometime later... Read ya, Phil > but it doesn't make a lot of sense, because slib alone without
> umb-scheme doesn't really make a lot of sense, does it? :-)
Yes, actually it does. It is not unthinkable to have only guile installed
and not umb-scheme and guile needs slib as well. Look into /usr/share/guile/.
Right now you have "a false dependency" of guile on umb-scheme. Interestingly
enough even while these links are present 'guile.init', which exists in
the current version of slib (2d5, released 2002-11-28 :-), seems to be missing.
Should I file that as a separate bug?
Also there is a long list of other Scheme implementations also supported by
slib and although they are not supplied by Red Hat somebody working with
one of these likely would not mind to have libraries handy.
Last, but not least, not forcing a hunt for documentation in some unexpected
places, by having it in "normal" locations and accessible through standard
tools, also would be nice.
|