After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 313246 - Issues/questions with gnome-2.12 moduleset
Issues/questions with gnome-2.12 moduleset
Status: RESOLVED FIXED
Product: jhbuild
Classification: Infrastructure
Component: module sets
unspecified
Other Linux
: Normal normal
: ---
Assigned To: James Henstridge
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2005-08-11 18:33 UTC by Elijah Newren
Modified: 2006-04-20 03:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Elijah Newren 2005-08-11 18:33:06 UTC
Kick me if you'd prefer I refiled this as one-issue-per-bug-report but these all
seemed so small that I thought I'd collect them:

1) gdl is listed twice, with conflicting dependencies:
  <cvsmodule id="gdl">
    <dependencies>
      <dep package="libgnomeui" />
      <dep package="librsvg" />
    </dependencies>
  </cvsmodule>
and
  <cvsmodule id="gdl">
    <dependencies>
      <dep package="glib" />
    </dependencies>
  </cvsmodule>
Seems like they need to be merged or have one replace the other.

2) pyorbit is listed as a dependency of gnome-python.  gnome-python is part of
the desktop release and pyorbit isn't, and gnome-python technically builds
without pyorbit (though with only a subset of gnome-python submodules). 
However, the wiki lists all gnome-python submodules as being in the release, so
maybe pyorbit should be in the desktop release too.  I don't know and can't get
an I-dont-know-either answer from anyone on the release-team list (though Murray
is out of town...). 
http://mail.gnome.org/archives/desktop-devel-list/2004-October/msg00360.html is
all I can find on the issue which doesn't help.  The page does suggest that you
would know, as does Vincent on r-t.  Should it be a hard dependency?

3) yelp no longer uses gtkhtml2; it can be removed from its dependencies.

4) evolution-exchange is part of the desktop release but isn't in the set; would
it be okay to add it?

5) perl bindings and java bindings are part of the gnome release but aren't in
the set, whereas python and c++ bindings are in the set.  It appears that the
java ones have been placed in a gcj.modules file.  Should the same be done with
the perl bindings or can they be placed in the gnome-2.12 moduleset?

6) librsvg won't compile without npapi.h, which comes from mozilla.  Should
mozilla be listed as a dependency for librsvg?
Comment 1 James Henstridge 2005-08-15 05:50:14 UTC
(1) Feel free to fix this.  The first definition looks like the right one
(although the second one is what would be used at the moment, which is wrong).

(2) pyorbit is used to bind any Gnome library that exposes CORBA APIs.  Without
it, most of gnome-python doesn't get built (including the libbonobo* and
libgnome* bindings), so it is a dependency for useful programs.

(3) yep. should be fixed.

(4) yep.

(5) I never added the Java bindings to the gnome modules file because no one
ever suggested it (or added them).  Probably best to ask the java-gnome
developers.  Same goes for the Perl guys.

(6) if it is a dependency, then yes.  If it's configure script passes without
mozilla but the build subsequently fails, then that's a librsvg bug, of course.
Comment 2 Elijah Newren 2005-08-15 16:03:56 UTC
Okay, I fixed (1), (3), and (4).

For (2), it sounds like pyorbit ought to be in the desktop release.  Granted,
it's probably too late for that for 2.12, but perhaps we should propose it for
2.13?  And in the mean time, would changing it to a suggests instead of a
dependencies be reasonable?

Okay, I'll bring up the bindings to the java-gnome and gtk2-perl developers.

As for (6), it turns out that mozilla is a conditional dependency for librsvg;
somehow it got through configure thinking it should require it without finding
the necessary includes.  So I'll need to look closer and file a librsvg bug.
Comment 3 James Henstridge 2005-08-16 03:16:42 UTC
re (2): gnome-python is not very useful if pyorbit is not available, so changing
it to <suggests> would not be appropriate.  You'd end up testing only a tiny
proportion of the gnome-python code in that configuration, which doesn't benefit
anyone.
Comment 4 James Henstridge 2006-04-20 03:58:23 UTC
I think the remaining issues here have been addressed with gnome-python being split up, so am closing the bug.