I'm using Arch Linux, so I can rather prepare PKGBUILDs (for cc65-svn c64-emulator-lib-git nes-emulator-lib-git nesicide-git nesicide-emulator-git) and post them here (I can't promise they'll get into AUR though). Would it be okay?
Any help is appreciated. What you've said is foreign to me, though, so I will need to consult the almighty google to educate myself. Blast Linux and all its incarnations!
Let me try to save the trouble for you.
In case you are familiar with Gentoo ebuilds (I saw a it mentioned in the About Nesicide window), Arch Linux's PKGBUILD is something similar (but more primitive) to them. It's like a script that will fetch the sources from the upstream, compile and install, but just specific to Arch Linux.
They are not the part of the official repos though, it's just another mechanism for people to install packages that doesn't exists in the official repos, and also serving as a tool for building from sources.
In fact, there are already several (orphan) PKGBUILDs
which I belive used to work with Nesicide 1. They require minimal changes, but there's a catch; the repos don't seem to be independent. I could have the packages
nesicide-c64-emulator-lib-git nesicide-emulator-lib-git nesicide-git nesicide-emulator-git
but it seems nes-emulator-lib requires nesicide sources. Which makes me consider: should I instead have single, monolithic package that will pull in everything. What do you think?
(edit: nesicide-emulator-git or nes-emulator-git?)