skeezix
Internal Development
The concatenation sucks, fully agreed; right before going with that idea, we'd tried using a catenated index and then catenating the chunks.. which is more or less exactly what zip does for comments and junk. But it was shoddy, and we thrashed around trying options,and decided to go for 'this is easy and dumb, we can replace it later'; but in software we all know how that works,.. 'shit lives forever'
But squash (or whatever, the payload container type doesn't matter much, since you can detect and mount it easy enough) + zip appended was really always the goal; someone run some tests.. if the zip handlers are smarter now, that could be the way to go (unless some completely drastic other idea comes up.) Zip for main container is same boat.. mounting the entire thing to RAM was madness.
If anyone mentioned it (I didn't have time to read up, sorry , the executable pnd idea is something else to consider; I fiddled with it, had it work (its not hard to do, the binfmt thing .. hell, you can enable it in current firmware easy enough), but of course it doesn't support much .. when it occurred to me that having documentation handlers and multiple executables in there, it pretty much killed off the executable pnd idea. (By which I mean ./my.pnd to run it directly.)
The documentation handling is not bad as it is, but its not great either; somethign else to mull over
Oh, and using .desktop is the way to go imho, or JSON .. we all hate XML At least the XML makes self validating easy; .desktop is goofy as heck too, but at least its common and semi-standardized; we can add a pile of extra fields for the meta we want. At the time we thoguht of it a bit late, but I seem to recall there were some things we didn't think we could shoe-horn into .desktop, but I couldn't think of what they were a couple years back when I was ondering wtf we'd done there
jeff
But squash (or whatever, the payload container type doesn't matter much, since you can detect and mount it easy enough) + zip appended was really always the goal; someone run some tests.. if the zip handlers are smarter now, that could be the way to go (unless some completely drastic other idea comes up.) Zip for main container is same boat.. mounting the entire thing to RAM was madness.
If anyone mentioned it (I didn't have time to read up, sorry , the executable pnd idea is something else to consider; I fiddled with it, had it work (its not hard to do, the binfmt thing .. hell, you can enable it in current firmware easy enough), but of course it doesn't support much .. when it occurred to me that having documentation handlers and multiple executables in there, it pretty much killed off the executable pnd idea. (By which I mean ./my.pnd to run it directly.)
The documentation handling is not bad as it is, but its not great either; somethign else to mull over
Oh, and using .desktop is the way to go imho, or JSON .. we all hate XML At least the XML makes self validating easy; .desktop is goofy as heck too, but at least its common and semi-standardized; we can add a pile of extra fields for the meta we want. At the time we thoguht of it a bit late, but I seem to recall there were some things we didn't think we could shoe-horn into .desktop, but I couldn't think of what they were a couple years back when I was ondering wtf we'd done there
jeff