Re: external dependencies



Hi,

> On 9/11/06, Elijah Newren <newren gmail com> wrote:
> > On 9/11/06, Matthias Clasen <mclasen redhat com> wrote:
> > The topic came up earlier, and I think there was a general consensus
> > that it is a good idea to freeze the versions of external dependencies,
> > and use tarball modules for them in the gnome-2.18 moduleset in jhbuild.

I would prefer to use the cvs/svn/whatever modules on the tag
corresponding to the release, if it exists. That way you can use your
jhbuild checkout to make patches (cvs diff), which is impossible for
tarball builds.

> I've put together a _preliminary_ page to help push these two ideas
> along at http://live.gnome.org/TwoPointSeventeen/ExternalDependencies.
> There may be inaccuracies or omissions there, but it has the basics
> already.  Thoughts?  Comments?

>From that lgo page:

> xulrunner (mozilla) 
> 1.5.0.6 
> http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.6/source/ 

The link points to the firefox source, not xulrunner.
While xulrunner 1.8.0 doesn't suffice for epiphany dependency (you need
some patches), xulrunner from the 1.8 branch (what the current jhbuild
moduleset is building: MOZILLA_1_8_BRANCH) does. There's going to be a
xulrunner 1.8.1 _release_ some time after the ff 2.0 release (see
http://benjamin.smedbergs.us/blog/2006-08-22/xulrunner-updates/ ), so I
think it should be safe to use that as the gecko dependency version for
epiphany for the Gnome 2.18 release.

Regards,
	Christian




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]