Re: Orca Dependencies Question

[Willie Walker <William Walker Sun COM>]

Hi Janina:

I'm learning along with you with respect to how to express the
dependencies in a spec file (and in the config file).  I've learned the
pkg-config utility can be your friend here, and spent some time editing
configure.in and orca.spec.in today to get things "right" (I hope!).
Your help here will go a long way, too, so I appreciate your time!

Here's an example of using pkg-config:

wwalker tecra:~/work/gnome-head/orca$ pkg-config --modversion gtk+-2.0
2.8.17

The latest configure.in and orca.spec.in are now in GNOME CVS HEAD.
They are hopefully better than what was there before.

Will

On Thu, 2006-05-04 at 16:09 -0400, Janina Sajka wrote:
> Willie Walker writes:
> > It may be.  I remain perplexed whenever I run into the various terms gtk
> > +, gtk+-2.0, and gtk2.  The thing we need is the GTK that is used by
> > GNOME 2.14.  I think "gtk+-2.0" is the right thing and the version we
> > care about is 2.8.16 or better.  The entry I put in the sample spec file
> > is an attempt to reflect this, and I pulled the line from other spec
> > files for other GNOME projects.
>
> I'll double-check on the fedora-devel list, but the only gtk+ in the
> Fedora repositories has filenames like gtk+-1.2.10-50, which I believe
> is Gnome 1.2 (or 1.4).
>
> On the other hand, with 'rpm -qlp [package.rpm]' you can list out what is contained within any
> given .rpm, and running that command gives a possibly long list of
> included files--275 in the case of:
>
> rpm -qlp gtk2-2.8.17-2.i386.rpm  |wc -l
>
> the latest gtk2 rpm on fedora's devel repository.
>
>
> > The big issue here, however, is how to reflect build requirements vs.
> > runtime requirements.  To build Orca, you need surprisingly little as
> > you discovered.  Python is a very dynamic language, however, that
> > resolves its dependencies at run time.  As such, you don't really
> > discover what's missing until you actually try to use it.
> OK. I'm beginning to grok this.
>
> > Because of the dynamic nature of Python, I leaned towards forcing the
> > runtime requirements to be build requirements in configure.in, and I
> > believe you are probably running into this.  I did this to try to avoid
> > users that scream "HEY! It built, but it won't run.  What did you guys
> > screw up?" when in fact the problem is that they didn't have the
> > necessary runtime requirements installed.
>
> Precisely what's happening here. So, the need is to identify runtime
> requirements in a form that the distro can satisfy. So, with rpm you can
> also do:
>
> rpm -q --whatprovides [module.so]
>
> to help with correct package identifiers. How easy is it to get a list of
> what Orca actually needs at runtime?
>
> Janina
>
> > Will
> >
> >
> > _______________________________________________
> > Orca-list mailing list
> > Orca-list gnome org
> > http://mail.gnome.org/mailman/listinfo/orca-list