The amarok-svn and amarok2-svn are packaging the same. And even if one of them would package svn version of amarok 1 it would not be necessary because the Amarok 1.x development was discontinued and thus amarok1 package is the only necessary for Amarok 1.4. 2009/7/3 Stefan Husmann <stefan-husmann@xxxxxxxxxxx>: > Manne Merak schrieb: >> >> Will Siddall wrote: >>> >>> Each of these packages are for a different purpose. Obviously >>> amarok-svn is to download the latest amarok from subversion, >>> amarok2-svn is so people get the latest build of amarok2 from >>> subversion and amarok1 would be for those people who want the 1.4.10 >>> build of amarok because they are reluctant to upgrade to 2 (such as >>> myself). >>> The update dates only reflect when the owner of the package made a >>> change to the package details, it does not reflect the application >>> itself (especially if it is coming from svn). >>> >>> If you want the latest application and you're using the svn packages, >>> new code is usually submitted every night, so run your update every >>> night for that package. >>> >>> Will >>> >>> On Fri, Jul 3, 2009 at 6:40 AM, Manne Merak<mannemerak@xxxxxxxxx> wrote: >>> >>>> >>>> Well, there is: >>>> amarok-svn >>>> amarok1 1.4.10-3 >>>> amarok2-svn >>>> >>>> I will use amarok2-svn. >>>> Manne >>>> >>>> >> >> Sorry, I am still confused. >> What is the difference between amarok-svn amarok2-svn. I thought the >> latest amarok is verson 2? >> >> Manne >> >> > Hello, > > I guess amarok 1 and amarok 2 are different programs. So it makes sense to > have seperate developement on both branches, and so two svn branches. > > If thi is an upstream decision, we can reflect it in AUR by haveing two > PGKBUILDs. > > Regards Stefan >
