Investigate packaging cores

[amstan]

Once #19 and #20 are finished, I can start looking at if I should/how i could package up all of mister's cores so they're managed by pacman.

Would be cool if I could select the following list of arch packages installed:

• mister-base, which will be a meta package automatically depending on
  • linux-mister
  • mister-bin
  • mister-menu
  • uboot-mister
• mister-computer-ao486
• mister-computer-zxspectrum
• mister-console-sms
• mister-presets

A couple group packages could be created too, which would be a way for users to list what's available:

• mister-arcade
• mister-computer
• mister-console
• mister-other
• mister-utility
• mister - a group of all the above and mister-base

Note that most/all of these new core packages map directly to mister-downloader filters. By the looks of it, every core is non-overlapping with other cores, but I guess I'll see that after creating all packages and try installing them at the same time (if i get file conflicts).

[amstan]

For now this is how a pkg/ looks like:

.
./mister-computer-ao486
./mister-computer-ao486/media
./mister-computer-ao486/media/fat
./mister-computer-ao486/media/fat/mister-computer-ao486
./mister-computer-ao486/media/fat/mister-computer-ao486/docs
./mister-computer-ao486/media/fat/mister-computer-ao486/docs/AO486
./mister-computer-ao486/media/fat/mister-computer-ao486/docs/AO486/README.md
./mister-computer-ao486/media/fat/mister-computer-ao486/games
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/MISTERFB.DRV
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/MISTERFB.INF
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/misterfs.exe
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/imgset.exe
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/sbctl.exe
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/modem9x.inf
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/mpuctl.exe
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/drv/sysctl.exe
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/boot0.rom
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/boot1.rom
./mister-computer-ao486/media/fat/mister-computer-ao486/games/AO486/boot1_opensource.rom
./mister-computer-ao486/media/fat/mister-computer-ao486/_Computer
./mister-computer-ao486/media/fat/mister-computer-ao486/_Computer/ao486_20220326.rbf
./mister-computer-ao486/.PKGINFO
./mister-computer-ao486/.BUILDINFO
./mister-computer-ao486/.MTREE

[amstan]

For now versioning is still a problem, though one idea is to look at the core.rbf itself and try to extract it from there.

The problem with this is that we'll be oblivious if anything changed without the core changing, which will mean no updates in those cases. That's why I left stuff like pkgrel in each of the individual packages (for manual bumping), otherwise it would have been more trivial to replicate all the PKGBUILDs.

Would have been much easier if upstream had a way to track this.