Enki should refer to Qutepart as Git submodule

[vi]

There are a lot of times when something being added to Qutepart and Enki together. They should be linked more strongly (because of not just "Enki uses Qutepart", but also "Enki and Qutepart are developed together").

Hovewer there are currently no good way to tie them together except by date. Bisecting Enki is also complixified by the need to manually adapt Qutepart for every step.

There should be submodule in Enki repository so that each time some new Enki commit depends on some new Qutepart commit, submodule gets updated.

That way after checking some intermediate version of Enki we will get the appropriate version of Qutepart.

If you really hate submodules, you can manually maintain Qutepart's commit ID in Enki's README (or something). It will be "poor man's git submodules".

[vi]

Now Enki and Qutepart as 2 separate projects and I'm not going to include Qutepart to Enki source package and installers.

You can keep it like this for stable versions/installers, but it is clear that Enki is not that separate from Qutepart during the development.

When you depend on some fix or new feature in "markdown" or "PyQt4", you update dependency version requirement in README. But it is not feasible to do for "Qutepart" because of during the development Enki's Qutepart minimum version gets updated too frequently.

So that it is feasible to update Qutepart minimum version in Enki's README only when doing a release version and track Qutepart-Enki bond using submodules during the development.

[andreikop]

• Currently Enki checks if Qutepart version is supported, and will notify you, if Qutepart is too old or too new
• Now Enki shows Qutepart version on About dialog
• You don't have to bisect Qutepart when you bisecting Enki and vise versa.
  1. In the majority of cases it is obvious, which project is buggy.
  2. When Enki is bisected - just keep the latest Qutepart installed. Will work in the majority of cases
  3. When Qutepart is bisected - it is tested with editor.py, without Enki
  4. I'm now actively covering both projects with tests, I do not expect bisects often.
• You don't have to include Enki and Qutepart hashes to an issue, just write 'latest'

I have nothing against submodules, I just don't see necessity in this case. I always update Qutepart and install to the system - and things work fine. Please explain, why submodule is necessary