[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] instances/examples for server-side install?
- From: "Nick Boldt" <codeslave@xxxxxxxxxx>
- Date: Thu, 11 Sep 2008 01:53:30 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=mfT7A1h+z97eu5q9b/dpqcmBUPOlafh1saXqaNnjtbSAXxo+lOTbaqIAlhZtM1EACB e9ZsIFf10X/e07vpTDI7ymbtu0NEvxKgyaQUu18tLWplyI2ddm8HE/Ujlkh3fRVifz0I 5I/nWKaVkY1Ou9uJ4HS18zXNOhiD4YkEc144g=
With the Update UI, you can only update your own copy of Eclipse, not
a shared one.
With the installer, you could create a shared install consisting of an
So, for a multi-user install, root currently has to either install via
zip + dropins, or use the installer to install to some folder, linked
from dropins. But should root want to "assemble" a product from SDK +
other projects (ie., everything in /opt/eclipse/plugins &
/opt/eclipse/features), the installer won't allow that.
Is this not a valid use case?
On Mon, Sep 8, 2008 at 9:33 AM, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:
> The installer is designed to lay down a new product from scratch. If you
> already have an Eclipse SDK installed, why don't you just install the extra
> stuff using Help > Software Updates > Available Software ... ? I don't see
> much value in enabling the installer for the "install into existing
> application" scenario since you can do this directly from within the