blob: 0256ce4ab87b51055e9638baa3dfd865893457bd (
plain)
1
2
3
4
5
6
7
8
9
|
<br><br><div class="gmail_quote">On Thu, Jan 13, 2011 at 2:01 AM, Frank Griffin <span dir="ltr"><<a href="mailto:ftg@roadrunner.com">ftg@roadrunner.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
No they won't. They won't know anything about the distinction between<br>
installing via RPM or via tarball. They'll look in rpmdrake for Eclipse<br>
initially, install it from there, and then use the normal Eclipse<br>
mechanism to install plugins. They'll do this because we tell them to<br>
use rpmdrake to look for software, and they'll do the plugins the way<br>
they're used to or the way the Eclipse docs tell them to.<br></blockquote></div><br>I don't agree with you at that point. I always take the tarball from <a href="http://eclipse.org">eclipse.org</a> (for eclipse) or <a href="http://netbeans.org">netbeans.org</a> (for netbeans) instead of the one's of repository provided by the distro.<br>
The reason is quite simple, the one's mentioned above are newer than the one's in the repos (often, not always but everywhere i looked for it, it was so)<br><br>But there may be people who will first look in rpmdrake or urpmi that's right, but not everybody.<br>
-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br>
|
