V: put v.c on repository

[musou1500]

I think it's better to put it on GitHub repository.
If it's available on this repository, contributors can....

• use old versions(when latest version not works)
• create PR
• check change history easily

[LouCle]

iirc v.c is going to be deprecated soon, so I really don't see the point

[musou1500]

@LouCle Where did you get that information?

iirc v.c is going to be deprecated soon

even if it's a fact, being able to see commit log is a big advantage for contributors.
additionally, I often faced compiler(v.c) issues during the last few days.
so, I think It will take a while to v.c is stabilized.

[medvednikov]

v.c is not going to be deprecated.

I'll create a separate repo for this to avoid polluting history here with hundreds of thousands of lines.

[musou1500]

@medvednikov I got it! this issue can be closed.
can I close it?

[medvednikov]

well it should be closed once there's that repo. so not yet

[musou1500]

ok. thank you.

[Chiiruno]

This will be great for packaging on package management systems like NixOS and GuixSD.

[AurelienFT]

https://github.com/vlang/v/pull/522/ shound resolve this.

[whoizit]

@AurelienFT how to compile it now? should be git submodule in v/compiler/vc i guess

[musou1500]

@whoizit

how to compile it now?

vlang/v.c is not created yet.
but, as far as I saw the PR, it seems that Makefile clone v.c.

should be git submodule in v/compiler/vc i guess

may be. but in the PR, v.c is not a submodule. just external repository.

[whoizit]

@musou1500 http://github.com/vlang/vc

[AurelienFT]

I don't think it should be submodule because it needed to build the basic project. I saw submodule for "extra features"

[musou1500]

@whoizit oh....sorry. I missed it.

[whoizit]

@AurelienFT I guess label is 0.2.0, not 0.0.2

[whoizit]

I mean 0.2

[AurelienFT]

@whoizit I just put the project name. I think add label + project name is overkill

[medvednikov]

Done: https://github.com/vlang/vc