Summary: | rcsparse-9999.ebuild fromcvs-9999.ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marijn Schouten (RETIRED) <hkbst> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | Keywords: | EBUILD |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.geocities.co.jp/SiliconValley-PaloAlto/3388/rbtree/README.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-ruby/rbtree/rbtree-0.2.0.ebuild
dev-ruby/fromcvs/fromcvs-9999.ebuild dev-ruby/rcsparse/rcsparse-9999.ebuild dev-ruby/fromcvs/fromcvs-9999.ebuild dev-ruby/rbtree-0.2.0 gem implementation |
Description
Marijn Schouten (RETIRED)
2007-04-04 12:48:28 UTC
Created attachment 115434 [details]
dev-ruby/rbtree/rbtree-0.2.0.ebuild
Created attachment 115450 [details]
dev-ruby/fromcvs/fromcvs-9999.ebuild
fromcvs cvs to git and hg converter
Created attachment 115451 [details]
dev-ruby/rcsparse/rcsparse-9999.ebuild
Created attachment 115572 [details]
dev-ruby/fromcvs/fromcvs-9999.ebuild
updated ebuild with scripts in /usr/bin/ which can be called from any directory, unlike previous ebuild.
Let's be straight. I think ruby herd is currently understaffed (maybe one or two active members). And I by myself don't like "9999" ebuilds. So it's unlikely I will add these ebuilds to the tree. If you are willing to maintain these, it could help testing them. I didn't mean for the 9999 ebuilds to be included, just the rbtree if you want it. Created attachment 172539 [details]
dev-ruby/rbtree-0.2.0 gem implementation
This version uses the gems.eclass, it works with Ruby 1.8 but fails with Ruby 1.9.
I see rbtree made it into the tree. Removing ruby herd since dev-ruby/rbtree has been in the tree since March 2009. Since I've been using these two for our test conversion from CVS to git I added them to the tree (with modifications for ruby-ng and other things). There were a few issues (ruby-ng and mercurial eclasses don't exactly get along) and I would appreciate someone checking if I didn't screw something up too bad. |