* bug#17030: CEDET EDE documentation mentions android project, but not in tree
@ 2014-03-18 0:14 Daniel Colascione
2014-03-18 7:17 ` David Engster
0 siblings, 1 reply; 9+ messages in thread
From: Daniel Colascione @ 2014-03-18 0:14 UTC (permalink / raw)
To: 17030
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
The CEDET documentation for EDE mentions ede-android-project, but this
facility is absent from the version of CEDET in mainline. It is,
however, present in the standalone CEDET distribution.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-18 0:14 bug#17030: CEDET EDE documentation mentions android project, but not in tree Daniel Colascione
@ 2014-03-18 7:17 ` David Engster
2014-03-18 7:19 ` Daniel Colascione
0 siblings, 1 reply; 9+ messages in thread
From: David Engster @ 2014-03-18 7:17 UTC (permalink / raw)
To: Daniel Colascione; +Cc: 17030-done
Daniel Colascione writes:
> The CEDET documentation for EDE mentions ede-android-project, but this
> facility is absent from the version of CEDET in mainline. It is,
> however, present in the standalone CEDET distribution.
Yes, thank you. I removed that node as well as references to
ede-java-root-project and ede-arduino, which are also only upstream.
-David
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-18 7:17 ` David Engster
@ 2014-03-18 7:19 ` Daniel Colascione
2014-03-18 7:32 ` David Engster
0 siblings, 1 reply; 9+ messages in thread
From: Daniel Colascione @ 2014-03-18 7:19 UTC (permalink / raw)
To: David Engster; +Cc: 17030-done
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
On 03/18/2014 12:17 AM, David Engster wrote:
> Daniel Colascione writes:
>> The CEDET documentation for EDE mentions ede-android-project, but this
>> facility is absent from the version of CEDET in mainline. It is,
>> however, present in the standalone CEDET distribution.
>
> Yes, thank you. I removed that node as well as references to
> ede-java-root-project and ede-arduino, which are also only upstream.
>
Thanks. Why *aren't* these facilities in mainline, though?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-18 7:19 ` Daniel Colascione
@ 2014-03-18 7:32 ` David Engster
2014-03-18 7:42 ` Dmitry Gutov
0 siblings, 1 reply; 9+ messages in thread
From: David Engster @ 2014-03-18 7:32 UTC (permalink / raw)
To: Daniel Colascione; +Cc: 17030-done
Daniel Colascione writes:
> On 03/18/2014 12:17 AM, David Engster wrote:
>> Daniel Colascione writes:
>>> The CEDET documentation for EDE mentions ede-android-project, but this
>>> facility is absent from the version of CEDET in mainline. It is,
>>> however, present in the standalone CEDET distribution.
>>
>> Yes, thank you. I removed that node as well as references to
>> ede-java-root-project and ede-arduino, which are also only upstream.
>>
>
> Thanks. Why *aren't* these facilities in mainline, though?
Because I'm not sure whether they are generally usable. Those features
haven't received much testing and are often honed to one specific setup.
-David
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-18 7:32 ` David Engster
@ 2014-03-18 7:42 ` Dmitry Gutov
2014-03-18 8:19 ` David Engster
0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Gutov @ 2014-03-18 7:42 UTC (permalink / raw)
To: Daniel Colascione; +Cc: 17030-done
David Engster <deng@randomsample.de> writes:
> Because I'm not sure whether they are generally usable. Those features
> haven't received much testing and are often honed to one specific setup.
Do you expect them to get much testing while not being included in Emacs?
As long as they don't eat users' files, I'd release them as-is and then
collect bug reports. This would've been better performed earlier in the
24.4 release cycle, though.
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-18 7:42 ` Dmitry Gutov
@ 2014-03-18 8:19 ` David Engster
2014-03-20 15:43 ` Dmitry Gutov
0 siblings, 1 reply; 9+ messages in thread
From: David Engster @ 2014-03-18 8:19 UTC (permalink / raw)
To: Dmitry Gutov; +Cc: 17030-done
Dmitry Gutov writes:
> David Engster <deng@randomsample.de> writes:
>
>> Because I'm not sure whether they are generally usable. Those features
>> haven't received much testing and are often honed to one specific setup.
>
> Do you expect them to get much testing while not being included in Emacs?
No, but it's better than merging half-baked code and waiting for bug
reports which probably won't get fixed.
> As long as they don't eat users' files, I'd release them as-is and then
> collect bug reports.
That doesn't work because there are not enough CEDET developers. Our
resources are stretched thin with maintaining the stuff that is already
in Emacs, so I'm not inclined to merge more, largely untested code which
I myself don't use.
However, if someone volunteers to act as maintainer for one those
packages, I'd merge them, although whoever wants to maintain the Android
project should make sure the head of the FSF is OK with it being in
Emacs, and I can't imagine anyone eager to start that discussion...
-David
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-18 8:19 ` David Engster
@ 2014-03-20 15:43 ` Dmitry Gutov
2014-03-20 16:45 ` David Engster
0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Gutov @ 2014-03-20 15:43 UTC (permalink / raw)
To: David Engster; +Cc: 17030-done
On 18.03.2014 10:19, David Engster wrote:
> That doesn't work because there are not enough CEDET developers. Our
> resources are stretched thin with maintaining the stuff that is already
> in Emacs, so I'm not inclined to merge more, largely untested code which
> I myself don't use.
I see. But why not merge db-javap.el, at least? And maybe related code.
Do you think Alex isn't going to support it?
> whoever wants to maintain the Android
> project should make sure the head of the FSF is OK with it being in
> Emacs, and I can't imagine anyone eager to start that discussion...
I think CEDET really needs to move to ELPA. Even if Richard would object
to distributing some code via GNU ELPA (but, as you can notice,
company-clang is still there, for now), the additional features
shouldn't be too hard to modularize and distribute separately.
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-20 15:43 ` Dmitry Gutov
@ 2014-03-20 16:45 ` David Engster
2014-03-20 17:16 ` Dmitry Gutov
0 siblings, 1 reply; 9+ messages in thread
From: David Engster @ 2014-03-20 16:45 UTC (permalink / raw)
To: Dmitry Gutov; +Cc: 17030-done
Dmitry Gutov writes:
> On 18.03.2014 10:19, David Engster wrote:
>
>> That doesn't work because there are not enough CEDET developers. Our
>> resources are stretched thin with maintaining the stuff that is already
>> in Emacs, so I'm not inclined to merge more, largely untested code which
>> I myself don't use.
>
> I see. But why not merge db-javap.el, at least? And maybe related code.
Do you use it? Last time I tried it (2012 or so), Java support had lots
of problems.
> Do you think Alex isn't going to support it?
I don't know. From what I can see in the logs, work on it has stalled.
>> whoever wants to maintain the Android
>> project should make sure the head of the FSF is OK with it being in
>> Emacs, and I can't imagine anyone eager to start that discussion...
>
> I think CEDET really needs to move to ELPA.
Maybe. That'd be worth discussing as soon as someone volunteers to do
the work.
-David
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#17030: CEDET EDE documentation mentions android project, but not in tree
2014-03-20 16:45 ` David Engster
@ 2014-03-20 17:16 ` Dmitry Gutov
0 siblings, 0 replies; 9+ messages in thread
From: Dmitry Gutov @ 2014-03-20 17:16 UTC (permalink / raw)
To: David Engster; +Cc: 17030-done
On 20.03.2014 18:45, David Engster wrote:
> Do you use it? Last time I tried it (2012 or so), Java support had lots
> of problems.
I at least would have properly tried it if it were in the core
distribution (or if it were distributed separately all the time; the
pre-loading approach is too ugly for my taste to keep in the init file).
I haven't been using Java for quite a while, but it's a language I can
see myself returning to in the future more likely than C/C++.
So it could be a likely entry point to the CEDET codebase, for me or
someone else.
>> Do you think Alex isn't going to support it?
>
> I don't know. From what I can see in the logs, work on it has stalled.
That's too bad. On the other hand, the only related issue I could find
(https://github.com/alexott/cedet/issues/1) is fixed and closed.
>> I think CEDET really needs to move to ELPA.
>
> Maybe. That'd be worth discussing as soon as someone volunteers to do
> the work.
Ok.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2014-03-20 17:16 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-18 0:14 bug#17030: CEDET EDE documentation mentions android project, but not in tree Daniel Colascione
2014-03-18 7:17 ` David Engster
2014-03-18 7:19 ` Daniel Colascione
2014-03-18 7:32 ` David Engster
2014-03-18 7:42 ` Dmitry Gutov
2014-03-18 8:19 ` David Engster
2014-03-20 15:43 ` Dmitry Gutov
2014-03-20 16:45 ` David Engster
2014-03-20 17:16 ` Dmitry Gutov
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).