I know that Nightingale isn't ready for a release yet, but I believe that attempting to package it now is important. It will be a proof of concept to counter the multiple web-site failures, and time elapsed since Songbird dropped its support of the G.N.U./Linux platform. At least, a spec file rpm building and a control file for deb building would be nice. If the given information is there for people to package, or test packaging, then that would help people think about using Nightingale as opposed to the tar-ball that is put out as an unsupported, contributed build from Songbird. The key to Nightingale's success is its integration into package management and integration into common desktop behavior (i.e. menus, non-local installation).
As mentioned in another thread, I am working on a BuildBot instance for Nightingale. So it would be possible to set up automated packaging as part of the build process. I will do some research into how this is normally done in BuildBot; my guess is just a series of Shell commands that directly emulate the manual build process. As for setting up the specifics of each build, I have no packaging experience whatsoever so any help is greatly appreciated!
This being the story maybe the project should start building from the Songbird repository. If the current project's repository is edited only by stevo and you are building the buildfactory then maybe repackaging the contributed builds for Linux should be the current goal so that when 1.10 is released (supposedly sometime in the first quarter of the year) there will already be a reasonable amount of knowledge ready to be applied to quickly packaging the next release. I have just started my hand at packaging.
What are the development file dependencies for Nightingale? Which distributions support them?
Is there a chart of the breakdown across all of the O.S. that we intend to support? If not, then maybe one should be made on the wiki. This would be a very nice way of organization solutions to future problems (i.e. Fedora will at least need RPMFusion repositories). Ubuntu probably won't have any licensing issue. For this reason, it might be beneficial to host rpm and deb for the different O.S. as well as inclusion in repositories (i.e. to support mp3 on Fedora it might be necessary to have to use the RPMFusion as the host repository).