Re: project.el semantics

[Stephen Leake <stephen_leake@stephe-leake.org>]

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 11/10/2015 08:00 AM, John Wiegley wrote:
>
>> I guess I'm just asking exactly what you'd like to discuss about the code. If
>> you want a review, then I know what's being asked for. Otherwise, is there an
>> open question that needs my comment? It seems to be developing along fairly
>> well.
>
> You can see we disagree about some things with Stephen, from the
> discussion. These issues relate to method names, docstrings and the
> FIXME that's in the file.

More precisely, the only hot issue is the semantics of
"package-library-roots" and "package-roots".

They provide the list of directories that are related to the user's
project in some way (contain code, or documentation, or dependencies
(other packages or libraries)).

One use for these is to provide the search path for grep, or for
locate-file (with some glue code).

I don't understand why we have both; one would be sufficient. I have yet
to see an actual use case that requires both.

Since we have both, I don't understand what directories go in one vs the
other.

The rationale seems to change each time I propose a different use case.

One way to move forward would be to start a manual section for
package.el, and capture use cases in it, so we could refer to them. Or
capture use cases in a design document, if we don't want them in the
user manual.

-- 
-- Stephe