On 25.09.2009 20:49, Panos wrote: > Hello to everyone! > > I had recently created a thread on bbs.archlinux.org here > > http://bbs.archlinux.org/viewtopic.php?id=79410 > > in order to discuss the situration for the numerous chromium packages on > AUR. > > As I can see, they are getting more and more. I would like to make the > discussion on mailing list so that more people would participate. > > The list: > > 1 aur/chromium-browser 4.0.204.0~svn20090831r24879-1 (369) > 2 aur/chromium-browser-4.0.219.3 4.0.219.3~svn20090925r27181-1 (0) > > 3 aur/chromium-browser-dev r26808-1 (107) > > 4 aur/chromium-browser-inspector r26919-1 (22) > > 5 aur/chromium-browser-l10n 4.0.219.0~svn20090924r27064-1 (6) > 6 aur/chromium-browser-svn `svn info /chromium/src/ | grep (8) > 7 aur/chromium-codecs-ffmpeg-nonfree r26428-1 (39) > 8 aur/chromium-continuous -latest (46) > 9 aur/chromium-fresh -latest (25) > 10 aur/chromium-snapshot 27035-1 [27188-1] (439) > 11 aur/chromium-snapshot-64 27164-5 (110) > 12 aur/chromium-snapshot-64-last -6 (40) > 13 aur/chromium-snapshot-latest -3 (4) > 14 aur/cxchromium 0.9.0-3 (153) > 15 aur/iron 3.0.197.0-6 (61) > > Except for 15 and 6 which provide a different package, and 14 which is very > old, all the others are differently packaged chromium from svn. > > Chromium in these packages comes from two sources: > > 1)build.chromium.org > 2)a deb from ppa.launchpad > > So I make the same question: do we really need all these packages ? Shouldn't > they be less and provide, from fewer PKGBUILDs, the different pre-packaged > chromium browser ? Because they are mostly repackaging an already packaged > chromium browser, except for (6). > > We have two chromium-browser that use a deb package --> shouldn't it be one ? > We have chromium-browser-dev --> it is the same as 1 and 2, but it can > repackage debs for both architectures. > 5 is a l10n package, it is only for the repackaged debs. > > We have 4 chromium-snapshot PKGBUILDs (they provide the one from > build.chromium.org ). Shouldn't there be only one, which will create a 32 or > 64 package from one PKGBUILD ? Just like chromium-browser-dev (which > repackages the deb one) and automatically ? > > As you can see, it is clearly a bit of a chaos here. > > > I agree that there's a lot of chaos here. Personally, I don't like any of the repackaged PPAs because it does not seem like a proper solution. I can testify that aur/chromium-browser-svn works very well and it is compiled from SVN directly on the user system. A directly source-built solution like that should be pursued. We don't need any more Ubuntu remixing, it only increases complexity and make for a problematic cross-arch distribution.
-- Sven-Hendrik
