Home » Language IDEs » C / C++ IDE (CDT) » new CDT driver for Eclipse V1.0 available
| | |
| Re: new CDT driver for Eclipse V1.0 available [message #11061 is a reply to message #11037] |
Thu, 17 January 2002 14:40   |
 C4Eclipse Team
Messages: 65
Registered: July 2009 |
Member |
|
|
I have updated the 20020116 driver with a new install.txt and
the todo.txt in the proper place. Here is the new section I
added to install.txt:
<snip>
Upgrading
----------
If you have a previous version of the CDT installed, you should remove it
before
installing the 20020116 driver. To do this, remove the CDT plugins from
your
eclipse/plugins directory if you are sure that you have not installed any
other
plugins whose names begin with "com.ibm".
rm -rf <some_dir>/eclipse/plugins/com.ibm*
If you have installed some other plugins whose names may also start with
"com.ibm", or if you are not sure, then only delete the following plugins:
com.ibm.cpp.docs.user
com.ibm.cpp.miners
com.ibm.cpp.miners.parser
com.ibm.cpp.ui
com.ibm.debug
com.ibm.debug.doc.user
com.ibm.debug.gdbPicl
com.ibm.dstore.core
com.ibm.dstore.extra
com.ibm.dstore.extra.server
com.ibm.dstore.hosts
com.ibm.dstore.miners
com.ibm.dstore.ui
com.ibm.linux.help
com.ibm.lpex
We will be providing an installer that will take care of this for you in
future
releases.
NOTE:
Since eclipse persists UI information, and fields or view names may have
changed,
it may be necessary to remove the metadata for the CDT plugins. If you find
some runtime exceptions from one of the above plugins, or plugins not being
loaded try the following:
1. From a shell, navigate to where you invoke eclipse from.
2. There should be a ".metadata" or "workspace" directory there.
3. Navigate down to the workspace/.metadata/.plugins directory.
4. Remove any directories that match the plugin names above.
If after trying this and restarting eclipse, the problems still exist,
You can try removing the entire ".metadata" directory. If the problems
still exist then open a bug at http://bugs.eclipse.org
</snip>
Thanks...
Jeff Turnham
"David Goodenough" <david.goodenough@btconnect.com> wrote in message
news:a26b0k$2ua$1@rogue.oti.com...
> David McKnight wrote:
>
> > There's a new CDT driver (20020116) for Eclipse V1.0 available here:
> > http://64.38.235.23/tools/cdt/downloads/
> >
> > Here's a summary of what's new in this driver:
> > -additional C/C++ declarations browsing support in the project
> > objects views (prompted by discussions in this newsgroup)
> > -confirmations for destructive actions (such as delete project as
> > reported here)
> > -more support for multiple selection based actions in C/C++ Projects
> > view
> > -improved command integration in the C/C++ Projects view menus
> > -performance improvements in the user interface and the parser
> > -proper icon integration
> > -enhanced autoconf, linux help and debugger support
> > -various bug fixes
> >
> > Dave
>
> In the readme.txt in the ZIP file, there is a reference to the
> accompanying todo.txt file, which does not seem to be present.
>
> For installation. install.txt describes the process for installing
> from scratch, but does not talk about upgrade. If I have an
> Eclipse system with CDT installed, should I delete the relevant
> plugin directories or can I simply unzip on top of what is already
> there?
>
> David
|
|
|
| Re: new CDT driver for Eclipse V1.0 available [message #12457 is a reply to message #11061] |
Thu, 17 January 2002 14:55 |
Peter Manahan
Messages: 131
Registered: July 2009 |
Senior Member |
|
|
That rm -rf statement is kind of dangerous if you dropped the cdt onto WSAD or
if there were any other com.ibm plugins that aren't part of the cdt. Could you
just add a list of the relevant plugin directories instead. Even better just
create a lil script that removes the "specific" cdt plugins.
Jeff Turnham wrote:
> I have updated the 20020116 driver with a new install.txt and
> the todo.txt in the proper place. Here is the new section I
> added to install.txt:
>
> <snip>
>
> Upgrading
> ----------
>
> If you have a previous version of the CDT installed, you should remove it
> before
> installing the 20020116 driver. To do this, remove the CDT plugins from
> your
> eclipse/plugins directory if you are sure that you have not installed any
> other
> plugins whose names begin with "com.ibm".
>
> rm -rf <some_dir>/eclipse/plugins/com.ibm*
>
> If you have installed some other plugins whose names may also start with
> "com.ibm", or if you are not sure, then only delete the following plugins:
>
> com.ibm.cpp.docs.user
> com.ibm.cpp.miners
> com.ibm.cpp.miners.parser
> com.ibm.cpp.ui
> com.ibm.debug
> com.ibm.debug.doc.user
> com.ibm.debug.gdbPicl
> com.ibm.dstore.core
> com.ibm.dstore.extra
> com.ibm.dstore.extra.server
> com.ibm.dstore.hosts
> com.ibm.dstore.miners
> com.ibm.dstore.ui
> com.ibm.linux.help
> com.ibm.lpex
>
> We will be providing an installer that will take care of this for you in
> future
> releases.
>
> NOTE:
>
> Since eclipse persists UI information, and fields or view names may have
> changed,
> it may be necessary to remove the metadata for the CDT plugins. If you find
> some runtime exceptions from one of the above plugins, or plugins not being
> loaded try the following:
>
> 1. From a shell, navigate to where you invoke eclipse from.
> 2. There should be a ".metadata" or "workspace" directory there.
> 3. Navigate down to the workspace/.metadata/.plugins directory.
> 4. Remove any directories that match the plugin names above.
> If after trying this and restarting eclipse, the problems still exist,
> You can try removing the entire ".metadata" directory. If the problems
> still exist then open a bug at http://bugs.eclipse.org
>
> </snip>
>
> Thanks...
>
> Jeff Turnham
>
> "David Goodenough" <david.goodenough@btconnect.com> wrote in message
> news:a26b0k$2ua$1@rogue.oti.com...
> > David McKnight wrote:
> >
> > > There's a new CDT driver (20020116) for Eclipse V1.0 available here:
> > > http://64.38.235.23/tools/cdt/downloads/
> > >
> > > Here's a summary of what's new in this driver:
> > > -additional C/C++ declarations browsing support in the project
> > > objects views (prompted by discussions in this newsgroup)
> > > -confirmations for destructive actions (such as delete project as
> > > reported here)
> > > -more support for multiple selection based actions in C/C++ Projects
> > > view
> > > -improved command integration in the C/C++ Projects view menus
> > > -performance improvements in the user interface and the parser
> > > -proper icon integration
> > > -enhanced autoconf, linux help and debugger support
> > > -various bug fixes
> > >
> > > Dave
> >
> > In the readme.txt in the ZIP file, there is a reference to the
> > accompanying todo.txt file, which does not seem to be present.
> >
> > For installation. install.txt describes the process for installing
> > from scratch, but does not talk about upgrade. If I have an
> > Eclipse system with CDT installed, should I delete the relevant
> > plugin directories or can I simply unzip on top of what is already
> > there?
> >
> > David
|
|
|
| Re: new CDT driver for Eclipse V1.0 available [message #12474 is a reply to message #12457] |
Thu, 17 January 2002 17:00 |
C4Eclipse Team
Messages: 65
Registered: July 2009 |
Member |
|
|
Hi Peter...I guess you stopped reading at the "rm -rf" command ;-) 2 lines
below that is the list of plugin directories, that you ask for. We should have
the installer ready to go very shortly, so that will make the removing happen
automagically.
"Peter Manahan" <manahan@ca.ibm.com> wrote in message
news:3C46E5E0.7D68AC8F@ca.ibm.com...
> That rm -rf statement is kind of dangerous if you dropped the cdt onto WSAD
or
> if there were any other com.ibm plugins that aren't part of the cdt. Could
you
> just add a list of the relevant plugin directories instead. Even better just
> create a lil script that removes the "specific" cdt plugins.
>
> Jeff Turnham wrote:
>
> > I have updated the 20020116 driver with a new install.txt and
> > the todo.txt in the proper place. Here is the new section I
> > added to install.txt:
> >
> > <snip>
> >
> > Upgrading
> > ----------
> >
> > If you have a previous version of the CDT installed, you should remove it
> > before
> > installing the 20020116 driver. To do this, remove the CDT plugins from
> > your
> > eclipse/plugins directory if you are sure that you have not installed any
> > other
> > plugins whose names begin with "com.ibm".
> >
> > rm -rf <some_dir>/eclipse/plugins/com.ibm*
> >
> > If you have installed some other plugins whose names may also start with
> > "com.ibm", or if you are not sure, then only delete the following plugins:
> >
> > com.ibm.cpp.docs.user
> > com.ibm.cpp.miners
> > com.ibm.cpp.miners.parser
> > com.ibm.cpp.ui
> > com.ibm.debug
> > com.ibm.debug.doc.user
> > com.ibm.debug.gdbPicl
> > com.ibm.dstore.core
> > com.ibm.dstore.extra
> > com.ibm.dstore.extra.server
> > com.ibm.dstore.hosts
> > com.ibm.dstore.miners
> > com.ibm.dstore.ui
> > com.ibm.linux.help
> > com.ibm.lpex
> >
> > We will be providing an installer that will take care of this for you in
> > future
> > releases.
> >
> > NOTE:
> >
> > Since eclipse persists UI information, and fields or view names may have
> > changed,
> > it may be necessary to remove the metadata for the CDT plugins. If you find
> > some runtime exceptions from one of the above plugins, or plugins not being
> > loaded try the following:
> >
> > 1. From a shell, navigate to where you invoke eclipse from.
> > 2. There should be a ".metadata" or "workspace" directory there.
> > 3. Navigate down to the workspace/.metadata/.plugins directory.
> > 4. Remove any directories that match the plugin names above.
> > If after trying this and restarting eclipse, the problems still exist,
> > You can try removing the entire ".metadata" directory. If the problems
> > still exist then open a bug at http://bugs.eclipse.org
> >
> > </snip>
> >
> > Thanks...
> >
> > Jeff Turnham
> >
> > "David Goodenough" <david.goodenough@btconnect.com> wrote in message
> > news:a26b0k$2ua$1@rogue.oti.com...
> > > David McKnight wrote:
> > >
> > > > There's a new CDT driver (20020116) for Eclipse V1.0 available here:
> > > > http://64.38.235.23/tools/cdt/downloads/
> > > >
> > > > Here's a summary of what's new in this driver:
> > > > -additional C/C++ declarations browsing support in the project
> > > > objects views (prompted by discussions in this newsgroup)
> > > > -confirmations for destructive actions (such as delete project as
> > > > reported here)
> > > > -more support for multiple selection based actions in C/C++ Projects
> > > > view
> > > > -improved command integration in the C/C++ Projects view menus
> > > > -performance improvements in the user interface and the parser
> > > > -proper icon integration
> > > > -enhanced autoconf, linux help and debugger support
> > > > -various bug fixes
> > > >
> > > > Dave
> > >
> > > In the readme.txt in the ZIP file, there is a reference to the
> > > accompanying todo.txt file, which does not seem to be present.
> > >
> > > For installation. install.txt describes the process for installing
> > > from scratch, but does not talk about upgrade. If I have an
> > > Eclipse system with CDT installed, should I delete the relevant
> > > plugin directories or can I simply unzip on top of what is already
> > > there?
> > >
> > > David
>
|
|
|
| Re: new CDT driver for Eclipse V1.0 available [message #12495 is a reply to message #12474] |
Thu, 17 January 2002 19:28 |
Peter Manahan
Messages: 131
Registered: July 2009 |
Senior Member |
|
|
heh whoops :)
Jeff Turnham wrote:
> Hi Peter...I guess you stopped reading at the "rm -rf" command ;-) 2 lines
> below that is the list of plugin directories, that you ask for. We should have
> the installer ready to go very shortly, so that will make the removing happen
> automagically.
>
> "Peter Manahan" <manahan@ca.ibm.com> wrote in message
> news:3C46E5E0.7D68AC8F@ca.ibm.com...
> > That rm -rf statement is kind of dangerous if you dropped the cdt onto WSAD
> or
> > if there were any other com.ibm plugins that aren't part of the cdt. Could
> you
> > just add a list of the relevant plugin directories instead. Even better just
> > create a lil script that removes the "specific" cdt plugins.
> >
> > Jeff Turnham wrote:
> >
> > > I have updated the 20020116 driver with a new install.txt and
> > > the todo.txt in the proper place. Here is the new section I
> > > added to install.txt:
> > >
> > > <snip>
> > >
> > > Upgrading
> > > ----------
> > >
> > > If you have a previous version of the CDT installed, you should remove it
> > > before
> > > installing the 20020116 driver. To do this, remove the CDT plugins from
> > > your
> > > eclipse/plugins directory if you are sure that you have not installed any
> > > other
> > > plugins whose names begin with "com.ibm".
> > >
> > > rm -rf <some_dir>/eclipse/plugins/com.ibm*
> > >
> > > If you have installed some other plugins whose names may also start with
> > > "com.ibm", or if you are not sure, then only delete the following plugins:
> > >
> > > com.ibm.cpp.docs.user
> > > com.ibm.cpp.miners
> > > com.ibm.cpp.miners.parser
> > > com.ibm.cpp.ui
> > > com.ibm.debug
> > > com.ibm.debug.doc.user
> > > com.ibm.debug.gdbPicl
> > > com.ibm.dstore.core
> > > com.ibm.dstore.extra
> > > com.ibm.dstore.extra.server
> > > com.ibm.dstore.hosts
> > > com.ibm.dstore.miners
> > > com.ibm.dstore.ui
> > > com.ibm.linux.help
> > > com.ibm.lpex
> > >
> > > We will be providing an installer that will take care of this for you in
> > > future
> > > releases.
> > >
> > > NOTE:
> > >
> > > Since eclipse persists UI information, and fields or view names may have
> > > changed,
> > > it may be necessary to remove the metadata for the CDT plugins. If you find
> > > some runtime exceptions from one of the above plugins, or plugins not being
> > > loaded try the following:
> > >
> > > 1. From a shell, navigate to where you invoke eclipse from.
> > > 2. There should be a ".metadata" or "workspace" directory there.
> > > 3. Navigate down to the workspace/.metadata/.plugins directory.
> > > 4. Remove any directories that match the plugin names above.
> > > If after trying this and restarting eclipse, the problems still exist,
> > > You can try removing the entire ".metadata" directory. If the problems
> > > still exist then open a bug at http://bugs.eclipse.org
> > >
> > > </snip>
> > >
> > > Thanks...
> > >
> > > Jeff Turnham
> > >
> > > "David Goodenough" <david.goodenough@btconnect.com> wrote in message
> > > news:a26b0k$2ua$1@rogue.oti.com...
> > > > David McKnight wrote:
> > > >
> > > > > There's a new CDT driver (20020116) for Eclipse V1.0 available here:
> > > > > http://64.38.235.23/tools/cdt/downloads/
> > > > >
> > > > > Here's a summary of what's new in this driver:
> > > > > -additional C/C++ declarations browsing support in the project
> > > > > objects views (prompted by discussions in this newsgroup)
> > > > > -confirmations for destructive actions (such as delete project as
> > > > > reported here)
> > > > > -more support for multiple selection based actions in C/C++ Projects
> > > > > view
> > > > > -improved command integration in the C/C++ Projects view menus
> > > > > -performance improvements in the user interface and the parser
> > > > > -proper icon integration
> > > > > -enhanced autoconf, linux help and debugger support
> > > > > -various bug fixes
> > > > >
> > > > > Dave
> > > >
> > > > In the readme.txt in the ZIP file, there is a reference to the
> > > > accompanying todo.txt file, which does not seem to be present.
> > > >
> > > > For installation. install.txt describes the process for installing
> > > > from scratch, but does not talk about upgrade. If I have an
> > > > Eclipse system with CDT installed, should I delete the relevant
> > > > plugin directories or can I simply unzip on top of what is already
> > > > there?
> > > >
> > > > David
> >
|
|
|
| Re: new CDT driver for Eclipse V1.0 available [message #12516 is a reply to message #12495] |
Thu, 17 January 2002 21:51 |
C4Eclipse Team
Messages: 65
Registered: July 2009 |
Member |
|
|
That's an example of what happens when a developer writes user documentation ;-)
I was assuming that that someone reading that section would read the whole
section before running any commands...pretty weak assumption considering that
when working with other products I just quickly scan readme's and install.txt's
looking for what commands I need to run ;-)
I'll fix that up, so that it's more obvious...
On another note, I am implementing a "stand-alone" installer that doesn't do
much more than remove existing CDT plugins and unzip the new ones (Actually
there's more sophisticated part to it that lets you navigate to a remote
machine, ftp the server piece there, unzip the server piece and run it...but
that's still just prototyped). Anyway I'm doing this since it looks like the
Update support in Eclipse V1 has changed dramatically for V2.
I notice Peter that you have been pretty active on the mailing list for the
Eclipse Update component. Do you have a feel for when the Eclipse V2 Update
support will be relatively stable? In particular, are the many changes you
suggested, such as using the Native Installers going to be put in the builds?
If so, I'll probably wait until the Update support is closer to stable before
spending time integrating with it.
Thanks...
Jeff Turnham
"Peter Manahan" <manahan@ca.ibm.com> wrote in message
news:3C4725C5.578860C8@ca.ibm.com...
> heh whoops :)
>
> Jeff Turnham wrote:
>
> > Hi Peter...I guess you stopped reading at the "rm -rf" command ;-) 2 lines
> > below that is the list of plugin directories, that you ask for. We should
have
> > the installer ready to go very shortly, so that will make the removing
happen
> > automagically.
> >
> > "Peter Manahan" <manahan@ca.ibm.com> wrote in message
> > news:3C46E5E0.7D68AC8F@ca.ibm.com...
> > > That rm -rf statement is kind of dangerous if you dropped the cdt onto
WSAD
> > or
> > > if there were any other com.ibm plugins that aren't part of the cdt.
Could
> > you
> > > just add a list of the relevant plugin directories instead. Even better
just
> > > create a lil script that removes the "specific" cdt plugins.
> > >
> > > Jeff Turnham wrote:
> > >
> > > > I have updated the 20020116 driver with a new install.txt and
> > > > the todo.txt in the proper place. Here is the new section I
> > > > added to install.txt:
> > > >
> > > > <snip>
> > > >
> > > > Upgrading
> > > > ----------
> > > >
> > > > If you have a previous version of the CDT installed, you should remove
it
> > > > before
> > > > installing the 20020116 driver. To do this, remove the CDT plugins from
> > > > your
> > > > eclipse/plugins directory if you are sure that you have not installed
any
> > > > other
> > > > plugins whose names begin with "com.ibm".
> > > >
> > > > rm -rf <some_dir>/eclipse/plugins/com.ibm*
> > > >
> > > > If you have installed some other plugins whose names may also start with
> > > > "com.ibm", or if you are not sure, then only delete the following
plugins:
> > > >
> > > > com.ibm.cpp.docs.user
> > > > com.ibm.cpp.miners
> > > > com.ibm.cpp.miners.parser
> > > > com.ibm.cpp.ui
> > > > com.ibm.debug
> > > > com.ibm.debug.doc.user
> > > > com.ibm.debug.gdbPicl
> > > > com.ibm.dstore.core
> > > > com.ibm.dstore.extra
> > > > com.ibm.dstore.extra.server
> > > > com.ibm.dstore.hosts
> > > > com.ibm.dstore.miners
> > > > com.ibm.dstore.ui
> > > > com.ibm.linux.help
> > > > com.ibm.lpex
> > > >
> > > > We will be providing an installer that will take care of this for you in
> > > > future
> > > > releases.
> > > >
> > > > NOTE:
> > > >
> > > > Since eclipse persists UI information, and fields or view names may have
> > > > changed,
> > > > it may be necessary to remove the metadata for the CDT plugins. If you
find
> > > > some runtime exceptions from one of the above plugins, or plugins not
being
> > > > loaded try the following:
> > > >
> > > > 1. From a shell, navigate to where you invoke eclipse from.
> > > > 2. There should be a ".metadata" or "workspace" directory there.
> > > > 3. Navigate down to the workspace/.metadata/.plugins directory.
> > > > 4. Remove any directories that match the plugin names above.
> > > > If after trying this and restarting eclipse, the problems still
exist,
> > > > You can try removing the entire ".metadata" directory. If the
problems
> > > > still exist then open a bug at http://bugs.eclipse.org
> > > >
> > > > </snip>
> > > >
> > > > Thanks...
> > > >
> > > > Jeff Turnham
> > > >
> > > > "David Goodenough" <david.goodenough@btconnect.com> wrote in message
> > > > news:a26b0k$2ua$1@rogue.oti.com...
> > > > > David McKnight wrote:
> > > > >
> > > > > > There's a new CDT driver (20020116) for Eclipse V1.0 available here:
> > > > > > http://64.38.235.23/tools/cdt/downloads/
> > > > > >
> > > > > > Here's a summary of what's new in this driver:
> > > > > > -additional C/C++ declarations browsing support in the project
> > > > > > objects views (prompted by discussions in this newsgroup)
> > > > > > -confirmations for destructive actions (such as delete project
as
> > > > > > reported here)
> > > > > > -more support for multiple selection based actions in C/C++
Projects
> > > > > > view
> > > > > > -improved command integration in the C/C++ Projects view menus
> > > > > > -performance improvements in the user interface and the parser
> > > > > > -proper icon integration
> > > > > > -enhanced autoconf, linux help and debugger support
> > > > > > -various bug fixes
> > > > > >
> > > > > > Dave
> > > > >
> > > > > In the readme.txt in the ZIP file, there is a reference to the
> > > > > accompanying todo.txt file, which does not seem to be present.
> > > > >
> > > > > For installation. install.txt describes the process for installing
> > > > > from scratch, but does not talk about upgrade. If I have an
> > > > > Eclipse system with CDT installed, should I delete the relevant
> > > > > plugin directories or can I simply unzip on top of what is already
> > > > > there?
> > > > >
> > > > > David
> > >
>
|
|
| | |
| Re: new CDT driver for Eclipse V1.0 available [message #12577 is a reply to message #12556] |
Fri, 18 January 2002 08:45 |
David Goodenough
Messages: 157
Registered: July 2009 |
Senior Member |
|
|
Peter Manahan wrote:
> We have to wait for Christophe to actually finish coding the framework. I
> will
> be adding an RPM native install for WSAD into the update mechanism and
> hopefully a windows installer one as well. I am hoping to be able to
> release the native install code to eclipse (but i don't know yet ).
>
> However once the install code is released I believe there is a simple
> unjar installer supplied as an example. You should be able to start with
> that. However since it doesn't exist yet you may want to wait.
>
> It will make install's far more consistent (everything I droned on about
> in the mailing list :).
>
> Peter
> Christophe Elek wrote:
>
>> "Jeff Turnham" <eclipsc@ca.ibm.com> wrote in
>> news:a27h3v$i7a$1@rogue.oti.com:
>>
>> > [snip
>> >
>> > I notice Peter that you have been pretty active on the mailing list
>> > for the Eclipse Update component. Do you have a feel for when the
>> > Eclipse V2 Update support will be relatively stable? In particular,
>> > are the many changes you suggested, such as using the Native
>> > Installers going to be put in the builds? If so, I'll probably wait
>> > until the Update support is closer to stable before spending time
>> > integrating with it.
>> >
>> > Thanks...
>> >
>> > Jeff Turnham
>> >
>> > [snip]
>>
>> Pretty soon, pretty soon ;-)
>> When it is ready for *consumption* we'll let the mailing list and
>> newsgroup know.
>> It will be great to have you , Jeff, take a look at it then...
>>
>> --
>> Christophe Elek
>> Eclipse Project
>> http://www.eclipse.org
I know that officially you do not support it, but PLEASE remmeber that
not all Linux users use RPM. I am a Debian user, and WSAD does install
using Alien (which converts RPMs into DEBs), but I have to do that
conversion manually. So if you start using RPM under the covers I am
going to be completely stuffed (to use a technical term). Maybe this
needs to be configurable, and maybe you could look at providing other
file formats?
David
|
|
|
| Re: new CDT driver for Eclipse V1.0 available [message #12597 is a reply to message #12577] |
Fri, 18 January 2002 16:58 |
Eclipse User |
|
|
|
Originally posted by: James_Moody.oti.com
"David Goodenough" <david.goodenough@btconnect.com> wrote in message
news:a28nfi$s45$1@rogue.oti.com...
> Peter Manahan wrote:
>
> > We have to wait for Christophe to actually finish coding the framework.
I
> > will
> > be adding an RPM native install for WSAD into the update mechanism and
> > hopefully a windows installer one as well. I am hoping to be able to
> > release the native install code to eclipse (but i don't know yet ).
> >
> > However once the install code is released I believe there is a simple
> > unjar installer supplied as an example. You should be able to start with
> > that. However since it doesn't exist yet you may want to wait.
> >
> > It will make install's far more consistent (everything I droned on
about
> > in the mailing list :).
> >
> > Peter
> > Christophe Elek wrote:
> >
> >> "Jeff Turnham" <eclipsc@ca.ibm.com> wrote in
> >> news:a27h3v$i7a$1@rogue.oti.com:
> >>
> >> > [snip
> >> >
> >> > I notice Peter that you have been pretty active on the mailing list
> >> > for the Eclipse Update component. Do you have a feel for when the
> >> > Eclipse V2 Update support will be relatively stable? In particular,
> >> > are the many changes you suggested, such as using the Native
> >> > Installers going to be put in the builds? If so, I'll probably wait
> >> > until the Update support is closer to stable before spending time
> >> > integrating with it.
> >> >
> >> > Thanks...
> >> >
> >> > Jeff Turnham
> >> >
> >> > [snip]
> >>
> >> Pretty soon, pretty soon ;-)
> >> When it is ready for *consumption* we'll let the mailing list and
> >> newsgroup know.
> >> It will be great to have you , Jeff, take a look at it then...
> >>
> >> --
> >> Christophe Elek
> >> Eclipse Project
> >> http://www.eclipse.org
>
> I know that officially you do not support it, but PLEASE remmeber that
> not all Linux users use RPM. I am a Debian user, and WSAD does install
> using Alien (which converts RPMs into DEBs), but I have to do that
> conversion manually. So if you start using RPM under the covers I am
> going to be completely stuffed (to use a technical term). Maybe this
> needs to be configurable, and maybe you could look at providing other
> file formats?
>
> David
....or at least a tarball in addition to the RPM.
james (another Debian user)
|
|
| | |
Goto Forum:
Current Time: Sun Dec 22 11:50:01 GMT 2024
Powered by FUDForum. Page generated in 0.04737 seconds |
] 
Search
Help
Register
Login
Home
