On Mo, 2011-08-29 at 16:33 +0200, Krzesimir Nowak wrote:
2011/8/26 Patrick Ohly <patrick.ohly(a)intel.com>:
> The rationale must be that "make dist" is intended to produce the same
> result, always, no matter what the environment or configure options are.
> Just guessing, though.
This sounds sensible. Going this path I'd say that there are two solutions:
1. Distribute README.html - that would need README.html to be always
generated and that in fact - a syncevo's dependency on rst2html, that
is - configure would end with an error if there is no rst2html.
2. Don't distribute README.html - then it would be generated if
rst2html existed on system.
Above solutions clearly contradict your conclusion about README.html
being distributed if it can be build.
"intention" instead of "conclusion" is a better word here ;-)
The goal was to have the file around when using source .tar.gz from
, because those are built in an environment where we
ensure that rst2html is around.
Let's go for option 2. README.packagers must be extended with a hint to
packagers that they now (SyncEvolution >= 1.3) should make rst2html a
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.