Quoting Shawn Grover <[EMAIL PROTECTED]>: > My understanding is that you can use RPM without issues (other than > standard > dependency concerns), but will likely need to update your world entries > manually. If anyone were to write an ebuild script for the package, it > would depend on what you have in your world entries. I'd probably try to > resolve the dependencies using emerge, then do the RPM. Then again, I > haven't had to manually do an RPM yet, so I don't know all the details.
I've never used Gentoo, but I'm guessing that if your just installing a single package that other packages that you will be emerging don't depend on, then you shouldn't have to mess around with emerge. You will get lots of dep. issues since the RPM database will probably be empty, but you can just install those deps with emerge and use an rpm --nodeps or rpm --force to install the rpm. Then when you run the binary you will find out if it still has any dep. issues. > I'll probably be tackling this same issue in the not too distant future, as > I'd like to run Samba 3.0. Last time I looked, there were no ebuild > scripts > for Samba 3.0 (final release). So, I'd be interested in hearing how this > goes for you. What's wrong with the good old ./configure;make;make install? Jesse
