On 2009-08-15, at 00:31, Abdulaziz Ghuloum wrote:
(and this should be in a GUI version as well).

Future work.
Agreed. GUI versions are for builders of IDEs (which I personally would never use); I just want to make sure that we expose all the functionality in a way that is usable to IDE builders.

2. The library manager should be bundled with the Scheme system, so that users don't have to do anything to get it going. The bundle should include programs such as wget, curl, bazaar, and/or git, whatever is needed to make everything work.

No. The library manager is a separate entity that's independent of any Scheme implementation. You only need one library manager to use. If each of Ikarus, Larceny, PLT, Ypsilon, IronScheme, Mosh, etc. installs all the tools, it would be a mess.
After reading this, I realized what I wanted is really to encourage downstream packagers to create metapackages that include the Scheme system and the library manager. The point is to make it possible to use a package manager to get a 1-click install of everything a person needs to be using Scheme productively. But that is out of scope of the library manager itself, I agree.

Windows (`Deficient By Design' (TM)) is another matter. But that just means that a Windows package simply has everything the user needs, and installing multiple Scheme systems does mean maybe installing multiple copies of curl. That's hardly new in the Windows world.

<versioning>

I agree in principle. It is, however, a horrible issue that's intrinsic to software itself. We should either go with something and live with the consequences, or ignore versioning completely for now and make it future work. Ignoring it for the time being may not be the worst thing, since we have only a few libraries and all of them are being actively developed. So, we can just say "give me the latest xitomatl" and it should work for the time being.
Agreed.

-- v


Reply via email to