PSA: Gem Owners - don't yank old gem versions

5 views
Skip to first unread message

Rob Reynolds

unread,
Aug 31, 2010, 4:46:36 PM8/31/10
to nu-net
This messes up anybody that depends on your gem. They have to go download the gem manually and that defeats the purpose of gems.

The yank command has a very specific use. It's not to clean up older versions.  Yank should only be used when there is something wrong with the gem. Nick Q will probably correct me if I am wrong here.

See the images below to see what I'm talking about.  Not picking on anyone, just a learning opportunity here. And we are all learning. 
____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder
YankedVersions.png
ErrorsTryingToUseDependency.png

Nick Quaranto

unread,
Aug 31, 2010, 4:48:57 PM8/31/10
to nu-...@googlegroups.com
Yeah, this is one huge problem with how gem dependencies are handled in general. I think the only way we can deal with it is hook into the dependencies we have in the database and warn you when you yank 'hey, did you know X and Y gem depend on this?'

Rob Reynolds

unread,
Aug 31, 2010, 7:54:44 PM8/31/10
to nu-...@googlegroups.com
So - Daniel corrected me that he yanked those versions due to them being bad gems. The reason they were bad. The gemspec files, etc needs to be ascii and not utf-8? I didn't realize that would cause a problem.

Bil Simser

unread,
Aug 31, 2010, 10:22:01 PM8/31/10
to nu-net
Will add it to the FAQ later.

I haven't seen the repository go up a new one yet so holding off on
updates until we see where that's going. I know we're moving the
issues list from YouTrack to github, but did we agree on the wiki too?

On Aug 31, 5:54 pm, Rob Reynolds <ferventco...@gmail.com> wrote:
> So - Daniel corrected me that he yanked those versions due to them being bad
> gems. The reason they were bad. The gemspec files, etc needs to be ascii and
> not utf-8? I didn't realize that would cause a problem.
>
> http://twitter.com/Tigraine/statuses/22658135374
> ____
> Rob
> "Be passionate in all you do"
>
> http://devlicio.us/blogs/rob_reynoldshttp://ferventcoder.comhttp://twitter.com/ferventcoder
>
>
>
> On Tue, Aug 31, 2010 at 3:48 PM, Nick Quaranto <n...@quaran.to> wrote:
> > Yeah, this is one huge problem with how gem dependencies are handled in
> > general. I think the only way we can deal with it is hook into the
> > dependencies we have in the database and warn you when you yank 'hey, did
> > you know X and Y gem depend on this?'
>
> > On Tue, Aug 31, 2010 at 4:46 PM, Rob Reynolds <ferventco...@gmail.com>wrote:
>
> >> This messes up anybody that depends on your gem. They have to go download
> >> the gem manually and that defeats the purpose of gems.
>
> >> The yank command has a very specific use. It's not to clean up older
> >> versions.  Yank should only be used when there is something wrong with the
> >> gem. Nick Q will probably correct me if I am wrong here.
>
> >> See the images below to see what I'm talking about.  Not picking on
> >> anyone, just a learning opportunity here. And we are all learning.
> >> ____
> >> Rob
> >> "Be passionate in all you do"
>
> >>http://devlicio.us/blogs/rob_reynolds
> >>http://ferventcoder.com
> >>http://twitter.com/ferventcoder- Hide quoted text -
>
> - Show quoted text -
Reply all
Reply to author
Forward
0 new messages