Re: ruby21 Port dependencies question

sha1e11eb7f9b807f5b7f3beb7c23a06803c7484aebc \ sha256 09414b2dedd098bab278a46bd9a10b9cf6b409e06bb90f40ae001d60fe015388 \ rmd160 a506d3bab411794799df46d8128984dd59abb8de -- kimura wataru ___ macports-dev

Re: [121692] trunk/dports/sysutils

;> +xinstall "${worksrcpath}/peco" "${destroot}/${prefix}/bin" >> +} > > There's no need for quotes around those variables; this isn't a shell > script. > > There should be no "/" before "${prefix}" be

Re: Proposal to introduce "port select ruby"

policy allows only single digit version numbers, like 1.10. -- kimura wataru ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Proposal to introduce "port select ruby"

Thank Ryan, On Mon, 04 Mar 2013 06:33:04 -0600, Ryan Schmidt wrote: > > On Mar 4, 2013, at 06:22, kimura wataru wrote: > >> Last month, ruby-2.0 was released. I think we need "port select ruby" >> before add port:ruby20. >> I made some patches for &quo

Proposal to introduce "port select ruby"

fix}/libexec/ ruby1.8/nanoc3 - port:rb-nanoc3 ruby1.9/nanoc3 - port:rb19-nanoc3 ${prefix}/etc/select/ruby base - port:ruby_select none - port:ruby_select ruby18 - port:ruby ruby19

Re: [103423] trunk/dports/lang/ruby19

, > gone to the Preferences window, to the Downloads tab, and upgraded > your command line tools. > -- kimura wataru ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [101775] trunk/dports/lang/ruby19/Portfile

Thanks Ryan, This configure error occurs only when universal binary specified (passing multiple archs for --with-archs optition to `configure`). There is no problem for building single arch ruby. I've requested to correct this error to the release manager of ruby-1.9. On Sat, 19 Jan 2013 00:

Re: [85659] trunk/dports/ruby/rb-pdumpfs/Portfile

-2". > > If this is licensed as "GPL 2 or later" then you would write "GPL-2+". > -- kimura wataru ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [74719] trunk/dports/ruby/rb-rcairo/Portfile

orts now. Is > this something that is applicable to all ruby ports? if so, should it > go into the ruby portgroup instead of into each portfile? > -- kimura wataru ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [70524] trunk/dports/ruby/rb-rabbit/Portfile

eed to check for it > anymore. That was only done during the transition to MacPorts 1.9.0. > -- kimura wataru ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: ruby_select port

t us on the proper way to write a >> select port, now that the select functionality is built into Macports? > > Just do the same as python_select does now. It's a bit of redundancy > that *_select does the same as 'port select

Re: ruby_select port

thon_select port. However, I don't really know > what I'm doing, and I'm guessing that the "ruby" and "ruby19" ports are > going to have to be modified for this to work -- and I don't maintain either > of them. Can someone(s) point me in the right

Re: suggestion: split rb-gnome into rb-glib2, rb-pango, ...

Thanks Ryan, I did this at r54785. On Tue, 28 Jul 2009 02:01:45 -0500, Ryan Schmidt wrote: > On Jul 28, 2009, at 00:40, kimura wataru wrote: > >> port:rb-gnome contains many ruby libraries and its dependencies >> are so many. I think that is not convenient such as install &

suggestion: split rb-gnome into rb-glib2, rb-pango, ...

2, rb-gnome-panel I have two questions. (1) port:rb-gnome is nomaintainer. who allows me to split the port? (2) in my plan, port:rb-gnome becomes a meta port like port:gnustep. (rename rb-gnome-all of my personal port to rb-gnome) How about this? -- kimura w

Re: ruby_select experimental implementation

Hi, On Thu, 23 Apr 2009 00:02:30 +0200, Rainer Müller wrote: > kimura wataru wrote: >> I write experimental ruby_select for ruby186 and ruby18. >> >> http://trac.macports.org/browser/users/kimuraw/ruby_select > > Will ruby19 be moved to ruby? Or what will happen to

Re: ruby_select experimental implementation

Hi Florian, On Fri, 24 Apr 2009 08:52:48 +0200, C. Florian Ebeling wrote: > On Wed, Apr 22, 2009 at 3:00 PM, kimura wataru wrote: >> I write experimental ruby_select for ruby186 and ruby18. >> >> http://trac.macports.org/browser/users/kimuraw/ruby_select > > I will

ruby_select experimental implementation

% ruby -rrbconfig -e 'p Config::CONFIG["LIBRUBYARG"]' "-lruby18" % ruby -rvendor-specific -rrbconfig -e 'p Config::CONFIG["LIBRUBYARG"]' "-lruby" so, port:rb-* links libruby.dylib and extension modules (.bundle) use ruby_selec

Re: Ruby upgrade missing defs

-0400, William Davis wrote: > here they are. this is in the latest change: > > No definition for bsock_do_not_rev_lookup > . > No definition for bsock_do_not_rev_lookup_set > . > No definition for bsock_s_for_fd -- kimura wataru ___

trunk "dropPrivileges" question(Re: ruby, macports trunk and setgid)

Hi, I reproduced the problem #19131 on ppc 10.4.11 with trunk r49611. but succeeded build on ppc 10.5.3 and i386 10.5.6. ruby port runs ruby(+miniruby) in build process, then ruby do not allow some options (-I, -r, -e,..) under uid <> euid or gid <> egid for security reasons. I tested `sudo port

Re: [48379] trunk/dports/ruby/rb-cocoa/Portfile

oa: fix #18708, add a variant "xcode". >> (snip) >> +destroot.violate_mtree yes > > What part of the port violates the mtree? Is it only the newly-added > xcode variant? If so, put the "destroot.violate_mtree yes" directive > inside the xcode variant. >

Re: [48379] trunk/dports/ruby/rb-cocoa/Portfile

ething like the following should work, unless there's > something obvious I'm missing: > > variant xcode description {blah blah blah} { > configure.args-append > --xcode-extras=${prefix}/share/doc/${name}/project-templates > } > > Also not

Re: [41224] trunk/dports/ruby/rb-cocoa

Thanks Ryan and Toby, I fixed rb-cocoa Portfile at r41309. On Tue, 28 Oct 2008 17:58:52 -0500, Ryan Schmidt wrote: >>> Could you change this to not use the cd command, please? The cd >>> command will >>> not be available in MacPorts 1.7.0 and later. Try: >>> >>> system "find ${worksrcpath} -typ

Re: Ruby ports and 1.9

tall > ruby libraries > via a generic package manager like mp, given that ruby has it's own in the > form of Rubygems, which even comes builtin with 1.9. > -- kimura wataru ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: lang/ruby: ignore minor system version for archdir, like Apple's Ruby

Florian > I agree. I comitted this change with your suggestion as r38064. http://trac.macports.org/changeset/38064 Thanks! -- kimura wataru ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

lang/ruby: ignore minor system version for archdir, like Apple's Ruby

--enable-pthread \ --without-tk \ --with-vendordir=${prefix}/lib/ruby/vendor_ruby +# ignore minor version for archdir, like i686-darwin9.0 +configure.env UNAME_RELEASE=${os.major}.0 destroot.target