Re: External Deps: update pwlib and opal version
- From: "Elijah Newren" <newren gmail com>
- To: "Damien Sandras" <dsandras seconix com>
- Cc: release-team gnome org, Luca Ferretti <elle uca libero it>, desktop-devel-list gnome org
- Subject: Re: External Deps: update pwlib and opal version
- Date: Wed, 6 Jun 2007 20:05:12 -0600
On 6/4/07, Damien Sandras <dsandras seconix com> wrote:
Le dimanche 03 juin 2007 à 23:19 -0600, Elijah Newren a écrit :
> On 6/2/07, Luca Ferretti <elle uca libero it> wrote:
> > Il giorno mar, 29/05/2007 alle 10.37 +0200, Luca Ferretti ha scritto:
> > > Current
> > > PWLIB: 1.10.7
> > > OPAL: 2.2.8
> > >
> > > Suggested
> > > PWLIB: 1.11.3
> > > OPAL: 2.3.2
> >
> > It seems[1] that latest released packages are 1.11.1 and 2.3.1 :-(
> >
> > [1] http://sourceforge.net/project/showfiles.php?group_id=80674
>
> As of a little while ago, Damien had agreed to upload recent opal and
> pwlib tarballs to ftp.gnome.org (see
> http://ftp.gnome.org/pub/GNOME/sources/opal/2.2/ and
> http://ftp.gnome.org/pub/GNOME/sources/pwlib/1.10/). That works a lot
> better than sourceforge for us. So the 'latest' packages for us are
> actually earlier than that.
>
> We need to either get updated pwlib/opal tarballs, or downgrade ekiga
> temporarily. Actually, I think I switched jhbuild to just build ekiga
> from tarballs precisely due to this super-strict pwlib & opal version
> dependency issue. Maybe that should just be reflected in the wiki,
> with the understanding that it can and will update quite often?
I plan to provide up to date tarballs of OPAL and PWLIB for the stable
branch of Ekiga (I am actually doing it).
However, the unstable branch of Ekiga (ie SVN Trunk) depends on the
unstable branch of PWLIB and OPAL (ie CVS HEAD) for which there are
rarely tarballs.
I will do what you will suggest.
Is there any way you can fix your dependencies to be e.g., opal >=
OPAL_REQUIRED rather than opal == OPAL_REQUIRED? That would be the
optimal fix.
Alternatively, if you could get unstable opal and pwlib tarballs
uploaded and hopefully rolled more often (whenever ekiga needs
something newer), that would at least allow us a path forward using
ekiga trunk, though the '>=' thing would be a far better solution.
Thanks Damien!
Elijah
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]