[Rubygems-developers] RubyGems API Docs

Richard Kilmer rich at infoether.com
Fri Dec 3 10:58:08 EST 2004

The whole API is public in that it is open source.  All the classes can be
manipulated by any person that wants (on their own machine, etc), and we
should publish it all so that someone who wants to fully understand/
contribute to the API can do so.  But you are correct that there is a subset
of the API that library developers that package stuff as gems need to
understand to be functional.  We will change the API over time as necessary,
attempt to always be backward compatible where possible,  and provide clear
direction on how to migrate in the event that compatibility is not achieved.


On 12/3/04 9:36 AM, "Mauricio Fernández" <batsman.geo at yahoo.com> wrote:

> On Fri, Dec 03, 2004 at 08:57:28AM -0500, Jim Weirich wrote:
>> I just realized that we have not published the RubyGems API docs anywhere.
>> There wasn't even a Rakefile task to generate the rdocs.
>> So I took the liberty of generating them and putting them out at
>> http://rubygems.rubyforge.org/rdoc (and added pointers on the RubyGems main
>> page).
> Is the API officially considered stable, i.o.w. are you going to commit
> to it?
> I thought that only a very small part of RubyGems was to be
> exposed through a public API: Gem::Cache, Gem::Specification,
> Gem::RemoteInstaller...

More information about the Rubygems-developers mailing list