Home » Newcomers » Newcomers » Callisto install without Update Manager
| Callisto install without Update Manager [message #159359] |
Mon, 03 July 2006 10:32  |
Eclipse User |
|
|
|
Originally posted by: joseph.preston.kirtland.af.mil
I have development systems that have no internet access. How can I do an
install of the Callisto bundle without using Update Manger? Generally for
Eclipse installs, I download to an internet accessible system, and
transfer files over by hand-- burn CD or USB thumb-drive.
Thanks!
|
|
| | | |
| Re: Callisto install without Update Manager [message #159415 is a reply to message #159409] |
Mon, 03 July 2006 15:11  |
| Eclipse User |
|
|
|
Noud,
This is why using the Update Manager is the preferred method for
installing Eclipse plug-ins... doing it manually can be complicated.
Installing Eclipse on a non-networked machine is not the usual use
case.
On 7/3/06, Noud deBrouwer <noud4@home.nl> wrote:
> Jeff Myers wrote:
> > Joe,
> >
> > You can download the individual components you're interested in
> > separately from their respective websites, then unzip them all to the
>
> i think the point is.. Calisto does reference it's parts in text but
> does not supply html-links to these named parts.
Links to all the Eclipse projects included in Callisto are on the
Customized install page:
http://www.eclipse.org/callisto/custom.php
>
> > same location and you should be good to go. Just be careful in making
> > sure you get all the required plug-ins for the stuff you're interested
> > in. For instance, if you want to install VE, you'll need to get
GEF and
> > EMF too. The download page for each project should list their
> > requirements, if any.
>
> nor do projects allways supply html-links to their requirements.
Which projects don't provide links to their requirements? You can open
enhancement requests for the projects to fix their websites here:
https://bugs.eclipse.org/bugs/enter_feature.cgi
>
> on a side note.. Jeff, why not publish the scm & release db-uri publicly
> iso f.i. those text-maps.
I have no idea what you're talking about here... too many acronyms.
All eclipse projects's source are publicly available on the eclipse
cvs server. The the project metadata used by the Callisto update site
in the update manager is here:
http://download.eclipse.org/callisto/releases/site.xml
> --Noud
>
>
> > Hope this helps,
> > - Jeff
|
|
|
| Re: Callisto install without Update Manager [message #159425 is a reply to message #159415] |
Mon, 03 July 2006 15:12 |
| Eclipse User |
|
|
|
Jeff Myers wrote:
> Noud,
>
> This is why using the Update Manager is the preferred method for
> installing Eclipse plug-ins... doing it manually can be complicated.
sounds pretty valid from just the Eclipse perspective, but does not
work in conjuntion w/ various package-ing/deployment systems in use,
such as f.i. pkgsrc, ports nor (S)RPM and maybe others, f.i., you know
if SMIT will be informed?
> Installing Eclipse on a non-networked machine is not the usual use
> case.
well..having a non-networked machine is the most adviced way of having
a secure machine.. ..besides or let alone what the machine is intented
to do, let that be f.i. running/supplying Eclipse.
the first remark i made herein, strikes me the most. does.
dunno if it even came to ALF attention.
the second remark .. the non-networked-security-issue is
more a stroke i made.
--Noud
>
> On 7/3/06, Noud deBrouwer <noud4@home.nl> wrote:
> > Jeff Myers wrote:
> > > Joe,
> > >
> > > You can download the individual components you're interested in
> > > separately from their respective websites, then unzip them all to the
> >
> > i think the point is.. Calisto does reference it's parts in text but
> > does not supply html-links to these named parts.
>
> Links to all the Eclipse projects included in Callisto are on the
> Customized install page:
> http://www.eclipse.org/callisto/custom.php
>
> >
> > > same location and you should be good to go. Just be careful in making
> > > sure you get all the required plug-ins for the stuff you're interested
> > > in. For instance, if you want to install VE, you'll need to get
> GEF and
> > > EMF too. The download page for each project should list their
> > > requirements, if any.
> >
> > nor do projects allways supply html-links to their requirements.
>
> Which projects don't provide links to their requirements? You can open
> enhancement requests for the projects to fix their websites here:
> https://bugs.eclipse.org/bugs/enter_feature.cgi
>
> >
> > on a side note.. Jeff, why not publish the scm & release db-uri publicly
> > iso f.i. those text-maps.
>
> I have no idea what you're talking about here... too many acronyms.
> All eclipse projects's source are publicly available on the eclipse
> cvs server. The the project metadata used by the Callisto update site
> in the update manager is here:
> http://download.eclipse.org/callisto/releases/site.xml
>
> > --Noud
> >
>
> >
> > > Hope this helps,
> > > - Jeff
|
|
| |
| Re: Callisto install without Update Manager [message #159457 is a reply to message #159432] |
Mon, 03 July 2006 16:38 |
| Eclipse User |
|
|
|
Jeff Myers wrote:
> Noud deBrouwer wrote:
>
>> Jeff Myers wrote:
>>
>>> Noud,
>>>
>>> This is why using the Update Manager is the preferred method for
>>> installing Eclipse plug-ins... doing it manually can be complicated.
>>
>>
>> sounds pretty valid from just the Eclipse perspective, but does not
>> work in conjuntion w/ various package-ing/deployment systems in use,
>> such as f.i. pkgsrc, ports nor (S)RPM and maybe others, f.i., you know
>> if SMIT will be informed?
>
>
> The effort to make Eclipse more easily compatible/consumable from
> various Linux packaging systems is this project here:
> http://wiki.eclipse.org/index.php/Linux_Distributions_Projec t
yes allready seen.
but it's nature is different/broughter the specifics we came to namely
package and deploy.
not to over-hint, Linux Distributions Project does prefer/endorse my point,
states the same point, being it's best to start w/ the archive file and
write packageing and thus deployement around such a fornamed Eclipse
project archive.:
http://wiki.eclipse.org/index.php/Linux_Distributions_Projec t/Proposal#Issue_One_.E2.80.93_Eclipse_Installation_on_Linux
the:
http://wiki.eclipse.org/index.php/Linux_Distributions_Projec t/Proposal#Issue_Three_.E2.80.93_Linux_Integration
i find even more correct and interesting, maybe just cause there the
person(s)power/time/fund issues do play up given the differences touched
between .. say a pkgsrc and a SRPM build, power/time/fund-footprint
conserning.
this brought me to:
http://www.redhat.com/archives/fedora-devel-java-list/2005-M arch/msg00022.html
http://svn.bagu.org/pluginbuilder/
http://ftp.debian.org/debian/pool/main/c/cdbs/
for me this all initiated from the eclipsebuilder so i now have headless
build..inside pkgsrc structure.
> I suggest signing up with their mailing list if you'd like to
> participate in the effort.
no..i suggest, what i did, hands-on study the field a bit more.
now/then read their mailing list archive.
> What is SMIT?
IBM's software packageing and deployment manager for IBM AIX.
> - Jeff
--Noud
|
|
|
Goto Forum:
Current Time: Tue Jul 22 02:22:37 EDT 2025
Powered by FUDForum. Page generated in 0.33897 seconds |
Home