Panos Filip schrieb:
On Sat, Sep 26, 2009 at 6:48 PM, Biru Ionut <biru.io...@gmail.com> wrote:
On 09/26/2009 05:49 PM, Panos Filip wrote:
I think he found the first PKGBUILD not good, and then, instead of fixing
it, he disowned it and uploaded another one.
Do you think it's a good idea to create a *wiki page* where we'll propose
a
universal way of building chromium packages ? Then, a TU or someone else
who
*can* maintain difficult PKGBUILDs, should upload them.
lets clean it :D.
i will let only one build from ubuntu ppa and only one build from google
bot.
I vote for chromium-browser-dev (ppa) and chromium-snapshot(google bot) and
chromium-browser-svn which is the only one that is building from source.
If chromium-browser-dev and chromium-snapshot doesn't have proper PKGBUILD
for building native 64/32 we should ask the maintainer do that well and if
he doesn't do that in couples of days, i will orphan it
what do you think about this?
--
Ionut
Good idea. Three PKGBUILDs only then.
The one is ready (chromium-browser-svn), so we don't have to take care about
it, it's OK.
The other two now: they must be autodownloading (like svn/git/cvs) the
zip(googlebot) or deb (ppa) and 32 or 64bit according to system's $CARCH
variable.
For the first one (googlebot), I already have a PKGBUILD ready for
suggestion. If the wikipage is going to be created, i'll post it.
For the second one (ppa), it's more difficult because, as I 've tried,
wget/curl/elinks (used in order to download the html code and parse it in
order to find the latest package), need a lot of commands to clear the html
code. And the names used by ppa are also huge.
Hello,
I do not know (and honestly, do not even care) of all the differences that might
be between teh versions, but do we really need the ubuntu version (ppa)? In
other cases, we probably have a package build from sources and at most _one_
other release from upstream. And additionally the really free one: iron. Let's
delete all the others.
Regards Stefan
