Quote:
Originally Posted by cfillion
@IXix
As X-Raym said, additional files are specified from the metadata header:
Code:
/*
* Version: 1.0
* Provides:
* ixix-functions.jsfx-inc
* YourPackage Data/background.png
* some_file_that_is_not_in_the_repository.pdf http://download/url
* [windows] ixix-functions-win32.jsfx-inc
*/
This tells ReaPack to install ixix-functions.jsfx-inc from the same directory as the current file, background.png from the "YourPackage Data" subfolder and some_file_that_is_not_in_the_repository.pdf from an external URL. ixix-functions-win32.jsfx-inc is only installed on computers running Windows.
There are two limitations on this: - Only one package can claim a specific file at a time (meaning that sharing files between packages sucks at this time and I have yet to find a good solution. Suggestions appreciated)
- Files cannot be installed outside of the repository's root directory
|
Nice. Great work.
Regarding limitation 2, does that mean that I'd need to set my repo root as "[AppData]/REAPER" in order to install files to both "[AppData]REAPER/Effects/IX/" and "[AppData]REAPER/Data/IX" ?
Limitation 1 sucks hard but I don't know enough about this stuff to suggest any solutions.
Quote:
Originally Posted by X-Raym
To be honest, not having a file extension is what is ugly...
|
Yes but that's the situation we have to deal with. As Tale pointed out, just renaming the plugins isn't a very good option, so it would be much better if the awkward extentionless files could be handled.