Redirecting ruby-net-ldap to net-ldap
While the ruby-net-ldap gem seems to be an out-of-date copy of the net-ldap gem, the docs at https://rubygems.org/gems/ruby-net-ldap, which are out-of-date as well, show up in (Google) search results.
I'm working on consolidating these gems and pointing/redirecting to net-ldap as the canonical gem and docs.
Is there any way to redirect requests for ruby-net-ldap to net-ldap? How should this be handled?
Thanks!
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by lsegal on 03 Jan, 2015 08:23 PM
Until ruby-net-ldap is removed from RubyGems (if that's the plan), there's no good way for RubyDoc.info to stop serving docs for this gem. Also note that the versions available for ruby-net-ldap are different from net-ldap, so there would be no way to redirect a user looking for 0.0.4 of this gem to net-ldap, as it stands.
Personally I wouldn't recommend removing the gem since legacy code might be relying on it. If search results are the only problem, I would just update links to not refer to this gem and it will be deprioritized in Google through regular means. If that's not feasible we could look at adding something to our robots.txt so Google stops trying to crawl it-- that would be the better approach IMO.
2 Posted by Matt Todd on 03 Jan, 2015 10:14 PM
Thanks for getting back to me so quickly!
Yeah, ruby-net-ldap was the legacy gem name but hasn't been maintained since 2006. However, most blogs and tweets and inbound links go to ruby-net-ldap instead of net-ldap which results in new users being exposed to (really) old docs and possibly installing really old versions of the gem. We don't control any of these links, and many are years old now; it'd be a fools errand trying to update every last link on the internet pointing to the old gem (at least, that's what my gut tells me).
I agree, deleting the gem would likely be a bad move. The robots.txt option sounds like a good first step.
I think on my end, since I *just* got ownership of the ruby-net-ldap gem (and realized it was a recurring problem), I could publish a 0.0.4.1(.final?) which updates docs to point to net-ldap and include a post-install message (http://guides.rubygems.org/specification-reference/#post_install_message).
Aside from that, I'll reach out to the RubyGems team to explore options.