| 1 |
Howdy, |
| 2 |
|
| 3 |
Can someone point me to any documentation on why ebuilds are |
| 4 |
being created for ruby gems? |
| 5 |
|
| 6 |
Gem is the a nice, easy to use, standard package manager for ruby. |
| 7 |
|
| 8 |
The problem that I see is if you install the same package via both |
| 9 |
gem and portage all sorts of bad things happen. For the curious, |
| 10 |
use gem to install rake, then portage to install rake, then try to |
| 11 |
use rake... Hint, emerge --unmerge is your friend. |
| 12 |
|
| 13 |
The real problem is when you now install a package that has |
| 14 |
ruby dependencies (example kazehakase-0.4.1). Real easy to |
| 15 |
to have portage trash your previous gem install. |
| 16 |
|
| 17 |
Wouldn't make more sense to have the ebuilds front-end gem vs. |
| 18 |
doing a config & make & make instlal? Then if you had installed |
| 19 |
via gem, then portage, the gem would just be re-installed, not |
| 20 |
installed differently. |
| 21 |
|
| 22 |
TIA, |
| 23 |
Roy |
| 24 |
|
| 25 |
-- |
| 26 |
|
| 27 |
echo "spzxAdjtdp/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge' |
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives