Update (01 Aug 2015): Here is the alternative approach answer and the solution for blog post:
I was always wondering, why Sitecore yet hasn't hosted Sitecore.Kernel and Sitecore.MVC on the NuGet?
This would have simplified our (developers') life in some way, as for today, we have to keep an additional /Libs folder and reference those 2 DLLs out of it (but couple others will serve good as well, for instance Lucene DLLs etc.). That could also simplify versioning and dependencies issues for us as soon as we still are using NuGet package management, so we now have 2 folders for references, highlighted below:
If they avoid doing that for licensing purposes - that seems quite strange as mentioned libraries are very little part of what Sitecore is, plus they may just supply obfuscated DLLs via NuGet and normal reflection-friendly via standard platform installation.
Here is what I have in my Libs folder and that I use and reference in small proof-of-concept project:
Dear Sitecore, if you read me, please consider using NuGET - today's industry standard for packaging and resolving dependencies .