Songbirdnest announced the end of Songbirds Linux Development (bug 139019). As a result a new Project has formed and this should be the place to maintain a new ebuild.
No, a bug is not “a place to maintain a new ebuild”; a bugzilla is not a forum. If you want to submit a working ebuild, fine, but if you just want to discuss about it, please don't do it here. Thanks.
(In reply to comment #1) > No, a bug is not “a place to maintain a new ebuild”; a bugzilla is not a > forum. make a quick search for new ebuild ;-) > If you want to submit a working ebuild, fine, ... Yeah i'm working on it, upstream isn't that clear about how to build it. I try to avoid a suggested 2GB svn checkout from songbirdnest ... hang on.
Created attachment 228733 [details] not jet finished ebuild Upsream suggests to fetch http://publicsvn.songbirdnest.com/vendor-binaries/trunk/linux-x86_64/ or i586, but thats a 2GB checkout. The current ebuild misses http://publicsvn.songbirdnest.com/vendor-binaries/trunk/linux-x86_64/mozilla/release/include/gfx/nsIImage.h which is not present on my system w/ xulrunner-1.9.2 or firefox 3.6.3.
Created attachment 228735 [details] build log
Hello, i've made some progress in compiling nighingale, by creating a songbird vcs ebuild, see http://svn.xmw.de/websvn/gentoo-overlay/media-sound/songbird/ . After hours of irc chat with AndrewL and Cloaky32_dll on #nightingale on irc.mozilla.org, we could switch to nightingale-cvs core on top of the partly binary songbird-vcs dependencies/vendor files ( http://svn.xmw.de/websvn/gentoo-overlay/media-sound/nightingale/nightingale-1.8.0_alpha1628.ebuild ). Both tarball and LiveVCS is supported. Next step is to switch to nightingale source dependencies/vendor files ... stay tuned.
maybe taking a look at Arch's AUR helps ? from my first glimpse they're fetching from the same source: http://aur.archlinux.org/packages.php?O=0&K=songbird&do_Search=Go
Michael why don't you commit this on sunrise?
There is a stable release of the Nightingale. Why we don't have an ebuild in Portage tree.
(In reply to comment #8) > There is a stable release of the Nightingale. Why we don't have an ebuild in > Portage tree. Because nobody has stepped up to make an ebuild and maintain it. Are you volunteering?
Created attachment 309075 [details] nightingale-1.11.0.ebuild My attempt at an ebuild which I made according to the Archlinux PKGBUILD (https://aur.archlinux.org/packages.php?ID=52721) and the included nightingale.mk file. Works but needs refining especially the configuration part.
Created attachment 309077 [details, diff] glib_2.31.patch Patch to build against glib >=2.31
Created attachment 352784 [details] nightingale-1.12.ebuild Here's the updated ebuild for the newest version. Would love to see this in portage.
(In reply to Shubhadeep Chaudhuri from comment #12) > Created attachment 352784 [details] > nightingale-1.12.ebuild > > Here's the updated ebuild for the newest version. > Would love to see this in portage. Thanks Shubhadeep, your ebuild works for me in a ~amd64 box
Created attachment 372966 [details] nightingale-1.12.1.ebuild Ugly hack to install nightingale 1.12.1
Created attachment 386446 [details] nightinggale-1.12.1.ebuild
