On Sun, 2007-06-17 at 16:47 -0600, Elijah Newren wrote: > On 6/16/07, Jaap Haitsma <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Overhere [1] are the versions of external dependencies listed. I'm > > guessing that the minimum version should be the one present in > > jhbuild. This way it can be checked if all the software builds with > > the minimum version. > > > > But for instance cairo has a minimum version of 1.2.2 at [1] but in > > jhbuild version 1.4.6 is build. (Which is also not the recommended > > version at [1]) > > We're kind of stuck in a funny middle ground. We want to be able to > test newer (e.g. cairo) releases to make sure they're solid when > adopted by the distros. However, we don't want to make GNOME > unbuildable with older releases if there's no reason to, so it makes > sense to lag the minimum build requirements. As you point out, if we > don't test with the minimum build requirements then it becomes > difficult to tell if they are really the minimum. So it's a tough nut > to crack, and I'm really not sure how to resolve this. For now, > though, I would prefer to see us testing the recommended versions of > external dependencies since those are the ones distros are likely to > adopt.
Have a build bot that builds with minimum requirements, another with recommended. Need to automate version extraction though or it will fall outdated too. behdad > Just my $0.02. > > Elijah > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list -- behdad http://behdad.org/ "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin, 1759 _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list