* rp_module_menus is no more - instead use rp_module_section with one of
- core (core packages)
- main (main packages - which will be installed by default in the image)
- opt (optional packages)
- exp (experimental packages)
- driver (driver packages)
- config (configuration packages / tools)
* The setup menu organises the data based on the above sections. more could be added in the future if needed. Packages (internally modules), can be added / configured / removed individually, or as entire sections.
* The setup menu will automatically detect if a binary is available to be installed. the nobin flag is no longer needed. modules that install directly from binary via aptInstall or via a prebuilt binary need to use an install_bin_ function instead of install_
* rp_module_section of type "config" will have the "gui_" function called first if it's available, otherwise a standard depends/sources/build/install/configure will be called
* configure is no longer used for "gui" configuration function - use gui_ instead. Had already started to move to this before, but now it is required.
initial environment from retropie_packages.sh so there is no duplication of functionality. However it might be even cleaner to have a core module that contains this stuff and perhaps another module for packages, so the root shell scripts become simplified.
de-duplication, and new packages can be added without having to manually add menu entries for them.
retropie_setup.sh calls retropie_packages with the parameter init, to load the arrays with the package information. this will also
allow some de-duplication of start up code between these two scripts later.
the rp_registerFunction now takes an additional parameter after the description which is in the format
I+command
where I= the menu you want it to appear in (2=source menu, 3=setup menu)
+ or - says whether the item will be enabled or disabled by default (for the source menus which uses checkboxes)
command is optional and sets the default command to pass to retropie_packages when building. for example in the setup menu
some options use "configure".
you can add multiple menu entries. eg for SNESDev to appear in the sources menu as well as setup menu, you could use
"2+ 3+configure"
in the sources menu it would download/build/install and in the setup menu it would just configure
the next step with this could besplit/separate out the packages to their own modules and have them dynamically included, so it is even easier to add new items without
having to edit the large cumbersome rp_registerFunction list
Major reorganization of folder structure and refactoring of
RetroPie-Setup Script. This is a major update and is not compatible to
the previous versions of RetroPie installations.
Jools Wills