Something occurred to me that I figured I would ask about, predominantly for the sake of it (read: fun).
Publicly available libraries and runtimes can be linked to, and need not be included in this file.
In my case, I am attempting to build my Santahack entry with my libal5poly library, which is far from complete. I intend to extend it while I develop my Santahack entry, adding generic code that isn't specific to my entry to the library instead where appropriate. It's not really clear if my library's code then has to become a part of my entry's submission size limits. Going deeper, what if I were to only add minor enhancements to the library and most of the code was untouched? Would it suffice to include e.g., a patch file for the library or would the entire "bulk" have to be included in the submission entry?
I think that it can be rightly argued that code that exists before the competition begins can be excluded, and code that is written during must be included, but how do you separate intertwined code? It could also be argued that a patch (assuming the patch size is sufficiently smaller than the library as a whole; else it's useless) is sufficient code-wise to turn the before into the after. This is, of course, assuming the distributor/end user has or can acquire a patch program (of course, patch is freely available for all platforms, as far as I know).
Like I said, there's no way that it's actually going to be a limiting factor in my participation, but I just thought I would bring it up for the sake of it. I realize that Santahack, as with all of our looming-deadline competitions are all in the spirit of fun, but this seems like an interesting question to raise.
As an extension to this, I suppose it's also reasonable to consider the implications of an open source library being actively developed while the competition is taking place. Would you be able to freely use new features that were developed during the competition (by a third party or otherwise), or not; and under what conditions?
- I'm absolutely certain that it wouldn't be a problem including the library code in the archive space-wise, though I might frown on it from a distribution model standpoint. I'm not concerned about size.
- There really isn't a bulk of anything yet.