Bug 158827 - devel/rubygem-rdoc: fix compatibility with ruby 1.8
Summary: devel/rubygem-rdoc: fix compatibility with ruby 1.8
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Steve Wills
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-12 11:30 UTC by Frank Wall
Modified: 2011-07-20 03:50 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Wall 2011-07-12 11:30:11 UTC
RDoc 3.6 is still compatible with ruby 1.8, although it was lately marked as BROKEN for ruby 1.8. The NetBSD guys have fixed the problem for pkgsrc:

http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/devel/ruby-rdoc/Makefile.diff?r1=1.1&r2=1.2&only_with_tag=MAIN&f=h
http://comments.gmane.org/gmane.os.netbsd.devel.pkgsrc.cvs/157338

Fix: 

The NetBSD guys have fixed the problem for pkgsrc:

http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/devel/ruby-rdoc/Makefile.diff?r1=1.1&r2=1.2&only_with_tag=MAIN&f=h
http://comments.gmane.org/gmane.os.netbsd.devel.pkgsrc.cvs/157338
How-To-Repeat: Try to install devel/rubygem-rdoc while having ruby 1.8 installed.

===>  Checking if devel/rubygem-rdoc already installed
/usr/bin/env  /usr/local/bin/gem18 install -l --no-update-sources --no-ri --install-dir /usr/local/lib/ruby/gems/1.8 /usr/ports/distfiles/rubygem/rdoc-3.6.gem -- --build-args 
Successfully installed rdoc-3.6
1 gem installed
Installing RDoc documentation for rdoc-3.6...
/usr/local/lib/ruby/1.8/rdoc/code_objects.rb:153: warning: regexp has invalid interval
/usr/local/lib/ruby/1.8/rdoc/code_objects.rb:153: warning: regexp has `}' without escape
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2011-07-12 11:30:26 UTC
Responsible Changed
From-To: freebsd-ports-bugs->ruby

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Stanislav Sedov freebsd_committer freebsd_triage 2011-07-12 20:17:36 UTC
> RDoc 3.6 is still compatible with ruby 1.8, although it was lately marked as BROKEN for ruby 1.8. > The NetBSD guys have fixed the problem for pkgsrc:

It actually installs fine for me if I just kill the
RUBY_VER=	1.9
line.

-- 
Stanislav Sedov
ST4096-RIPE

()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments
Comment 3 Frank Wall 2011-07-13 13:57:34 UTC
On Tue, 12 Jul 2011 12:17:36 -0700, Stanislav Sedov wrote:
> It actually installs fine for me if I just kill the
> RUBY_VER=	1.9
> line.

Well, that's true. My mistake, I've only changed that line to "1.8"
and this really broke it. By simply removing the line it works like a 
charm.

Would you mind removing RUBY_VER from the port's Makefile? Lately 
pgollucci@
was adding the above line, but it seems to me like it's only causing 
trouble:

http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/rubygem-rdoc/Makefile.diff?r1=1.3&r2=1.4

So maybe you need to talk to pgollucci@ before changing anything.


Thanks
- Frank
Comment 4 Frank Wall 2011-07-14 16:47:27 UTC
On Wed, 13 Jul 2011 14:57:34 +0200, Frank Wall wrote:
> Well, that's true. My mistake, I've only changed that line to "1.8"
> and this really broke it. By simply removing the line it works like a 
> charm.

Unfortunately, my tinderbox told me that the problem still exists.
Though you can workaround it by calling `make install` twice. I
guess this is why it did work for me on the second try.

Take a look at the log:
http://pastebin.com/jbcei4yq

This takes me to the conclusion that we're still running into
this kind of bootstrap problem that the NetBSD people also
needed to fix for rdoc 3.6:
http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.cvs/157474

$ uname -a
FreeBSD 7.3-RELEASE-p2 FreeBSD 7.3-RELEASE-p2 #0: Mon Jul 12 19:23:19 
UTC 2010     
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
$ pkg_info -xI ruby
ruby+nopthreads-1.8.7.302,1 An object-oriented interpreted scripting 
language
ruby18-bdb-0.6.6    Ruby interface to Sleepycat's Berkeley DB revision 
2 or lat
ruby18-gems-1.7.2   Package management framework for the Ruby language
rubygem-rdoc-3.6    RDoc produces HTML and command-line documentation 
for Ruby


Thanks
- Frank
Comment 5 Philip M. Gollucci 2011-07-14 16:51:38 UTC
On 07/14/11 15:47, Frank Wall wrote:
> http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.cvs/157474
Yes, rdoc needs rdoc to install.  The 1st install bombs the ruby rdoc.
Thats why the second one works.  I've had some emails with steve@ about
this (and a hack to try to fix it).



-- 
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354
VP Infrastructure,                Apache Software Foundation
Committer,                        FreeBSD Foundation
Consultant,                       P6M7G8 Inc.
Sr. System Admin,                 Ridecharge Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
Comment 6 Steve Wills freebsd_committer freebsd_triage 2011-07-20 03:00:58 UTC
Responsible Changed
From-To: ruby->swills

I'll take it.
Comment 7 dfilter service freebsd_committer freebsd_triage 2011-07-20 03:44:35 UTC
swills      2011-07-20 02:44:26 UTC

  FreeBSD ports repository

  Modified files:
    devel/rubygem-rdoc   Makefile 
  Log:
  - Fix build with Ruby 1.9
  - Avoid overwriting rdoc and ri from ruby port (not perfect solution but
    best I can find at the moment)
  - Hints from NetBSD pkgsrc
  
  PR:             ports/158827
  
  Revision  Changes    Path
  1.6       +8 -2      ports/devel/rubygem-rdoc/Makefile
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 8 Steve Wills freebsd_committer freebsd_triage 2011-07-20 03:45:16 UTC
State Changed
From-To: open->closed

I think this is fixed now. Please let me know if you encounter issues.