2014-08-23, 03:10
Hello,
I am new to developing for XBMC (err..."Kodi" ), and since I'm currently struggling with the build deps scripts, I thought I would improve them, for the general good of the community. The first thing I've done is to add support for specifying a custom mirror (the default mirror happened to be down when I was first trying to download Kodi's dependencies). I've since thought of a couple of other improvements that I think people would like:
Question:
One thing that caught my attention is that there are two kinds of packages on the "deps" mirrors: (1) those that have been pre-packaged to be unzipped directly into the xbmc file system ("formed" packages), and (2) those that need post-processing. According to the comments in the 0_packagelist.txt file, the "formed" packages are the "new" way, whereas the others are "old". Is the intention to convert all of the old-style packages into the new "formed"-style packages, and then do away with the old ones entirely? Assuming this is the desired direction to go, I would be willing to do the work of repackaging the old ones to use the new package structure. I'd just need to know how/where to upload the new ones to be distributed to the mirrors.
If the "old" packages were all converted to the "new" package structure, then I think I could coalesce everything down to just one or two batch files...there'd be no need for a separate get_formed.bat, for example. Having it all in one script would make it much easier to do a good job of reporting errors to the user (passing information between batch files is...hard).
Thoughts?
I am new to developing for XBMC (err..."Kodi" ), and since I'm currently struggling with the build deps scripts, I thought I would improve them, for the general good of the community. The first thing I've done is to add support for specifying a custom mirror (the default mirror happened to be down when I was first trying to download Kodi's dependencies). I've since thought of a couple of other improvements that I think people would like:
- Writing the detailed spew (e.g., the output of 'unzip' commands) into a log file rather than the console
- Colorizing important text (such as "download failed"), so that it's more noticeable
- Reporting a list of failed packages at the end of the script, so that if there were any errors, these are made clear to the developer
Question:
One thing that caught my attention is that there are two kinds of packages on the "deps" mirrors: (1) those that have been pre-packaged to be unzipped directly into the xbmc file system ("formed" packages), and (2) those that need post-processing. According to the comments in the 0_packagelist.txt file, the "formed" packages are the "new" way, whereas the others are "old". Is the intention to convert all of the old-style packages into the new "formed"-style packages, and then do away with the old ones entirely? Assuming this is the desired direction to go, I would be willing to do the work of repackaging the old ones to use the new package structure. I'd just need to know how/where to upload the new ones to be distributed to the mirrors.
If the "old" packages were all converted to the "new" package structure, then I think I could coalesce everything down to just one or two batch files...there'd be no need for a separate get_formed.bat, for example. Having it all in one script would make it much easier to do a good job of reporting errors to the user (passing information between batch files is...hard).
Thoughts?