[CRIU] [PATCH 0/2] crit core-dump feature, v2

[Cyrill Gorcunov]

On Thu, Apr 30, 2015 at 11:07:32AM +0300, Ruslan Kuprieiev wrote:
> I can't agree that we should move core-dump outside as it is a logical part
> of CRiu Image Tool -- it
> transforms CRIU images into another form of saving state - core dump.  I'm
> also afraid that making
> core-dump feature standalone will make it harder for users to get it. If it
> will be a part of crit -- users
> will get everything in one package. It is also quite handy to have all
> criu-images-related stuff under one
> command - crit.
> 
> P.haul analogy doesn't work here, as p.haul is a completely separate project
> with a complex logic inside
> and can't be united with anything in the main criu repo. Core-dump, in it's
> turn, is a far less complex
> and is a part of CRIT, which we ship along with criu, so I see no reason why
> we should keep core-dump
> outside criu repo and outside CRIT.

Dunno, Ruslan, the core-dump may be a part of criu (for example I'm still
hoping to move our make engine into a separate project and use it as a
git submodule), but simply living in a separate repo (still be on criu.org)
with you as a project maintainer.

The thing is that -- we can't live without crit (because as I said we
rely on its "view" feature) but as to core-dump is not that obvious
to me. So I leave it up to Pavel. Personally I can live with both
in- and out- of repo choise, but prefer the last.