[Rubygems-developers] Uninstalling gems that other gems depend on

Gavin Sinclair gsinclair at soyabean.com.au
Mon Apr 26 11:07:01 EDT 2004


On Monday, April 26, 2004, 9:51:55 PM, Chad wrote:


> On 26/4/2004, at 2:15 AM, Gavin Sinclair wrote:

>> On Monday, April 26, 2004, 12:53:26 PM, Chad wrote:
>>
>>> I just checked in a change that will prompt the user when attempting
>>> to
>>> uninstall a gem that other gems may depend on.  It needs a lot of
>>> polishing and testing.  See what you think.
>>
>> That's good, because my additions to install a library stub will need
>> polishing and testing as well :)
>>
>> I just want to record the fact that uninstalling a gem does not
>> currently remove any application stubs pointing to that gem.
>>
>>> Sorry I haven't been keeping up for the past few days.  I've been 
>>> under
>>> the proverbial weather.  I know I've got emails left unanswered.  My
>>> apologies.
>>
>> No worries.
>>
>> Looks like it could be next weekend for the release.  Want to prepare
>> a trial release (but not release it) just to make sure everything
>> hangs together?
>>
>>

> Good idea.  I don't see why we can't release something today or 
> tomorrow, actually.  Here's a CVS export of the tag, release_0_3_0_pre.
>   See how it works for you.

> http://chadfowler.com/rubygems-0.3.0-pre.tar.gz

Well, it unpacks and installs OK.  Were you thinking to release it as
0.3-pre or 0.3?  I'd like to get the library stub working for 0.3,
but have no objection to a pre-release.

Cheers,
Gavin



More information about the Rubygems-developers mailing list