blob: 39918b990723a182dd416fb5df2542109874480e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
<br><br><div class="gmail_quote">On Thu, Jan 13, 2011 at 12:49 PM, Frank Griffin <span dir="ltr"><<a href="mailto:ftg@roadrunner.com">ftg@roadrunner.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
Daniel Kreuter wrote:
<blockquote type="cite"><br>
I don't agree with you at that point. I always take the tarball from <a href="http://eclipse.org" target="_blank">eclipse.org</a> (for
eclipse) or <a href="http://netbeans.org" target="_blank">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>
</blockquote>
<br>
Well, I didn't say *everybody*, I was referring to newer users who
might actually do what we tell them to :-)<br>
<br>
The problem is that there is a very high probability that anyone who
installs from an RPM will then install plugins directly.� Given that, I
would question even packaging the base product as an RPM.<br>
<br></div></blockquote></div>I agree with you. I think it's better to build just the basic ide with it's plugins and let the user install the rest via the Eclipse Marketplace (like Subclipse e.g.).<div>But we should consider that some of the plugins will have dependencies which won't be installed via the Marketplace like javaHL which is needed by Subclipse.<br clear="all">
<br>-- <br>Mit freundlichen Gr��en<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br>
</div>
|
