If I understand well, when you will publish it, the first merge requests you will receive will be improvements of your build system. People will compete to provide the best fix for this obvious deffect. As a result, the main brake for publication will disappear quickly.
> People will compete to provide the best fix for this obvious deffect.
This may be part of the concern. Sometimes for a personal project you don't want that sort of input on the essentials. It is your thing, you want to do it right yourself either through pride or because you feel you'll learn more/better that way.
In those cases, while being perfectly willing to share the results by releasing the source at a particular point they might not want to be "distracted" at this stage by the sort of input you describe.
Not releasing immediately also delays the potentially discombobulating license choice issue, if this is your first such project and you have not given that much thought previously.
