Re: [Cooker] Firefox3 beta for 2008.1??

[Vincent Danen]

* [2008-04-30 11:54:30 +0200] Giuseppe Ghib? wrote:

> Vincent Danen ha scritto:
> > * [2008-04-29 22:52:06 +0200] Tomasz Pawe?? Gajc wrote:
> >
> > > Well it works fine here, anyways i think i've messed up file list in
> > > last commit.
> > >
> > > I have two ideas:
> > > 1. Stick to a fake libification, which i add to latest
> > >     commit. I think it is pointless to define major as a
> > > current version of firefox.
> > >
> > > 2. Drop "mozilla" from %{name}, just to be close with upstream name.
> > >
> > >
> > > No problem, i've just made(i hope) a good startfor you to play with
> > > ff 3.0.
> >
> > At the same time, can we please stop with versioned libs or figure out a
> > way so that everything that uses firefox as a buildrequires doesn't need
> > to be recompiled every time we push an update?
> >
> > It seriously looks like we're the only ones who push such retardedly
> > large updates everytime a new ff/tb comes out, and it's really past time
> > to fix that.
> The way is pretty easy. Just provide a selfcontained firefox3 with all the
> libraries needed into /usr/lib/, without having to share any library of 
> firefox in libification
> of libmozilla-firefox3xxx, libmozilla-firefox3xxx-devel or something like 
> that.
> It's not obeyed to share even the latest drop of library. A conditional 
> flag in SPEC file
> would allow to work with a common SPEC file even for 2009.0 where the 
> libification process is due.
>
> In this way you can easily provide a 'firefox3' package as an added value 
> for 2008.1, without
> risking to mess up the entire distro. From who have to just use firefox 
> IMHO this is enough. The other distro packages
> which are linked with older libmozilla-firefox2xxx will continue to use 
> that one. Let's say it's an intermediate
> way between downloading the binaries from the mozilla.org site and use in a 
> stanalone dir
> in your $HOME (which will lack of menu entries, etc.), and a full libified 
> firefox which would require extra recompilation.

One day firefox2 will no longer be supported and we will have to use
firefox3 on the older distribs or risk having to patch firefox manually
which is something I wouldn't wish on anyone.

I personally don't see this as being optional.  We *have* to deal with
this somehow.  Frankly, using xulrunner would be best and the arguments
of lack of manpower don't make sense to me... it seems like it's *more*
effort to have to rebuild and test every bloody firefox-dependent
package every 2-3mos when a new version comes out that is the most time
wasting.

Maybe I should use the lack of manpower execuse and push every second or
third firefox update because we don't have enough manpower to rebuild
and test these things?

--
Vincent Danen @ http://linsec.ca/

Attachment: pgp00063.pgp
Description: PGP signature