Re: Project detection and configuration (Was: IDE)

[Dmitry Gutov]

On 10/14/2015 06:58 PM, Lluís wrote:

> * Repository
> ** Detect the root directory that conforms a checked-out repository
> ** Ignore repository-specific files on other components
> ** Interact with repo-management tools?

You might want to look at lisp/progmodes/project.el in the current 
master, if you haven't already.

> * Project information
> ** Name, version, homepage, etc

I think these are very low priority.

> * Build system
> ** This one seems rather tricky to provide a unified interface
> ** Detect autotools, hand-made makefiles, ant, maven, linux, etc.
> ** Build modes of a project (e.g., debug vs release)
> ** Generate files (targets) of a project
> ** Create release tarballs?

I'd rather have a flat list of tasks, so that different tasks could do 
many of these things.

Do we really need to be able to know, programmatically, that a certain 
task is related to the "debug" build? Otherwise, it would simply be to 
the build tool integration to include (or not) "debug" in the returned 
task name.

> ** Sometimes identifies the root directory of the project

When it does, a project implementation will have to handle this. Using 
`locate-dominating-file' or `file-exists-p' is not hard.