Well, I can report that the above didn't work.
After some experimentation and re-reading of the link I posted in response to cim, I think I understand why, and it's not good.
After the Linux Ext2 filesystem, directory structures were changed from a linear array of directory entries to a hashed, balanced, binary-tree (or htree) to improve performance. In simple terms, this means that for Ext3 and Ext4 filesystems, there
are no 'slots' left free when a directory or file is deleted.
Instead, the name of the file or directory is run through an algorithm to produce a "hash" or unique number. The value of this hash then determines which branch and leaf the entry for that file/directory will appear in. No matter how much shuffling around is attempted by adding/deleting files and directories, when you re-install an OXP, it will appear in the same position, relative to the other OXPs, that it had before.
It gets a bit more complicated than that, of course, but the upshot is that there is no way to predict where in the hash-tree a particular entry will appear, and thus currently there is no way to control (or alter) the loading order of OXP files in Linux.
The ramifications for OXPs which modify other OXPs, (such as BGS) will take some thinking about.
Svengali wrote:The loading order is - as far as I'm aware - OS specific and can't be specified by OXPs and Oolite uses what the OS filemanager tells it. So whatever OXPs are doing it might or might not work.
@ cim.. Is there any way that Oolite
can specify to the OS filemanager how it wants things loaded? Is that even necessarily a good idea, or may it lead to other problems? As filesystems continue to evolve, it may well become necessary that Oolite have a standardised method/system of loading OXPs, to maintain consistency across platforms.
The above also explains why Eric's Mac has a sorted list even when the ls -f option is used. Apple's HFS+ uses a simpler binary-tree structure, so the way a directory is stored on disk is quite different. When he lists a Linux Volume, he gets the same hash-sorted list as a Linux user.
In the meantime, guess I'll just have to follow Svengali's advice, and add the Halsis sounds to the BGS customsounds.plist.