I would like to submit plan9port  packages for tinycore.
I currently have a package with a script that downloads the latest version (tip, there are no releases), compiles it, and create the corresponding package. I would like to know what is preferred, to include the package with the installer, or to include the generated packages.
On the one side, the script is very small and would require (almost) no maintenance, while the packages would need to be updated with some frequency (but not too much, p9p changes very slowly nowadays). These packages would take much more disk space in the repos (about 70Mb). On the other hand, with the installer package, people would need the compiletc packages (I don't think this is a crazy requirement for potential p9p users) and would have to wait to compile them, which can take a bit long.
In case compiled packages are preferred, then we would have to decide how to split them, if at all. I know the standard here is separating doc and devel packages and so on, but these limits can become fuzzy when talking about p9p. There is some partitioning already defined by p9p, but in fact a user would need to load most of them to do anything. In my opinion, a huge package would be more practical, but it goes against all the tinycore guidelines, so this may be another argument for the script.
What would you suggest? I am more inclined for the installer, but any idea will be appreciated.