tin gherdanarra <tinman31337@...> writes:
> If I make a package to "just work" with sbcl, for example,
> CLOCC or araneida, will you guys include it in the standard
> distribution of SBCL so that users can just key in
> "(asdf-install:install 'araneida)", step back
> and use it?
Um... no. The official distribution of SBCL is intentionally
relatively low-maintenance, while providing the tools for users to
install what they want. So, if you make packages that just work with
SBCL, then making them available to other users is a matter of editing
CLiki pages so that the asdf-install utility knows where to find your
package. You should probably first discuss this with the maintainers
of the external software that you wish to make available, though.
> Will my documentation be included in the official sbcl
> documenation? Will *every* package I contribute make
> it into the official distribution, even obscure ones?
Packages that are distributed with sbcl, in general, are those which
firstly provide sufficiently sbcl-only utility that it makes no sense
to consider them as packages for general use, and secondly have a
commitment for ongoing maintenance. So, only those packages for which
those criteria are met will be distributed. This, I hope, will not
stop the development of a self-sustaining ecosystem of non-official
software based on and around sbcl; it's entirely possible also that
value-added redistributors of sbcl may consider such packaging to be
part of their interest, and assist in such building.