A least 5 people ask us every day when Amarok 2 will be ready and when it will be easy to install without compiling it - since yesterday we can tell them: there you go!
Project Neon makes it possible for YOU and me and everyone (kind of, at least ;-)
Neon is meant to provide nightly Amarok builds ....
which means that it generates new Amarok packages for various distributions (currently only Kubuntu, openSUSE is in the queue though) ever day so that everyone can install them for whatever reason (testing, checking out the latest development, ...).
... So the main aim of Neon is clearly to provide a way to install the latest Amarok development version.
After installing amarok-nightly you will find an entry in your application menu, I'd like to call that well integrated with the operating system ;-), but the nifty thing about it is, that amarok-nightly will run without problems along a production system, it is stored in a completely unrelated path and all configurations are (or rather should) be stored in it's own directory.
This makes it possible to check out Amarok 2 once a day while running Amarok 1 to get the usual music entertainment.
More information on Neon and how to use it are available on it's wiki page.
Later I will write a more technical post, explaining how it works and how to get other distributions supported.
Posts
8 Comments:
It might make sense for you to use the OpenSuse build service for the nightly builds - it has much CPU power and can provide packages for all common distributions (Ubuntu, Fedora, Mandriva, and of course OpenSuse).
In case you would start using it for shipping for example OpenSuse rpms I could help to extend this to Fedora, for example.
I wonder if it would be much work to convert the ubuntu script into a debian script or if no conversion is needed at all and the ubuntu packages can be used straight away on debian systems.
One question: doesn't Amarok 2 depend on some KDE 4.1 bits? How are these handled?
luca: yes, and of course these are provided by Neon as well! :-)
Might be me, but this looks a bit too weird for Hardy+KDE4 installed:
sudo aptitude install amarok-nightly
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following NEW packages will be automatically installed:
amarok-nightly-kdebase-runtime amarok-nightly-kdelibs amarok-nightly-qt amarok-nightly-strigi amarok-nightly-taglib comerr-dev flex hspell
libaudio-dev libcupsys2-dev libdbus-1-dev libexpat1-dev libfontconfig1-dev libfreetype6-dev libgcrypt11-dev libgl1-mesa-dev libglib2.0-dev
libglu1-mesa-dev libglu1-xorg-dev libgnutls-dev libgnutlsxx13 libgpg-error-dev libice-dev libjpeg62-dev libkadm55 libkrb5-dev liblcms1-dev
liblzo2-dev libmng-dev libopencdk10-dev libpng12-dev libpq-dev libpthread-stubs0 libpthread-stubs0-dev libqt0-ruby1.8 libsm-dev
libtasn1-3-dev libx11-dev libxau-dev libxcb-xlib0-dev libxcb1-dev libxcursor-dev libxdmcp-dev libxext-dev libxfixes-dev libxft-dev
libxi-dev libxinerama-dev libxmu-dev libxmu-headers libxrandr-dev libxrender-dev libxt-dev mesa-common-dev x11proto-core-dev
x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev x11proto-xinerama-dev
xtrans-dev
The -dev packages shouldn't be needed if you aren't hacking on any components. I bet that they are 'recommiended' and that aptitude is pulling them in automatically. See what happens with apt-get. Otherwise, yes, there will be 5 or so packages because Amarok2 is now running kde trunk, meaning qt4.4 snapshots and kde4.1 snapshots, so it will need to pull in its own kde/qt libraries. I'm in the same boat here.
Secondly, I've tried neon here and on my desktop, and in both places none of the icons showed up in Amarok2. My laptop uses Hardy with Gnome, my desktop has Kubuntu kde4 installed but I'm currently running with kde4.1 through kdesvn-build. Any thoughts on why this is?
spam, Amarok needs KDE 4.1, so having KDE 4.0 installed is irrelevant.
Andrew, Well part of the point of Neon is to setup a KDE4 development environment. And also to not have an overly complicated packaging system (since it has be rebuilt every night), so it doesn't split off the headers from like amarok-nightly-kdelibs. Thus it pulls in all the other -devels.
I've been running this on Kubuntu 8.04 with the regular KDE 4.0.3 packages and the only bug I've found is that all text in the application is rendered in a light blue color that is almost unreadable aainst the default application color. Shouldn't Amarok's color scheme change along with KDE's?
Now that I think about it, that's using some non-backported 4.1 features, right?
@Andrew: The missing icons is also present when trying to run from within KDE 3.5.9, I do believe it has something to do with svg rendering.
Post a Comment