Orca Dependencies Question

I've built an rpm for installing Orca 0.2.3 and would be
happy to make
it publically available, but it won't install as currently
configured
for lack of 8 dependencies. These 8 dependency packages
aren't even
available in the Fedora development repository yet.

So, here's my question.

Before I go out and build an rpm to satisfy these 8
dependencies, may I
please ask whether Orca is really requiring features not
present in
slightly older versions of these 8 packages? If so, I'll
happily do the
grunt work to stay current. But, if not, can we possibly
loosen up on
the requirements specifications?

An example:

The orca-0.2.3 configuration lists a dependency on
gnome-speech-0.3.10.
Is it actually using some feature of gnome-speech-0.3.10 not
present in
0.3.9? Or will it run just as well with the older
gnome-speech?

Please understand I'm not complaining. I'm just trying to
figure out how
best to participate as an early user, and as a minor
contributor.I'm
trying to figure out how to fill the gap providing rpms
until such time
as Fedora has picked up Orca support.

Here's the dependency list that can't currently be met
from Fedora
development rpm repositories:

Finished Dependency Resolution
Error: Missing Dependency: eel > 2.14.0 is needed by
package orca
Error: Missing Dependency: gnome-python2 >= 2.14.0 is
needed by package orca
Error: Missing Dependency: python(abi) = 2.4 is needed by
package orca
Error: Missing Dependency: gnome-speech >= 0.3.10 is
needed by package orca
Error: Missing Dependency: gtk+-2.0 >= 2.8.16 is needed
by package orcaError: Missing Dependency: libnetsnmp.so.9 is
needed by package kdeutils
Error: Missing Dependency: libgtop-2.0.so.0 is needed by
package gnome-applets
Error: Missing Dependency: libnetsnmp.so.9 is needed by
package openhpi
Error: Missing Dependency: libnetsnmp.so.9 is needed by
package php-snmp
Error: Missing Dependency: libgtop-2.0.so.0 is needed by
package gnome-python2-libgtop2
development rpms:


-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com

Marketing the Owasys 22C talking screenless cell phone in
the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janinafreestandards.org		http://a11y.org
_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

Hi Janina:

> I've built an rpm for installing Orca 0.2.3 and would
be happy to make
> it publically available,

Yeah!

>  but it won't install as currently configured
> for lack of 8 dependencies.

Darn!

>  These 8 dependency packages aren't even
> available in the Fedora development repository yet.

Are you using Fedora Core 5?  Because of the large number of
crasher and
other bug fixes that went into GNOME 2.14 across a number of
GNOME
components, we're now requiring GNOME 2.14, which I think
is what comes
with Fedora Core 5.

> The orca-0.2.3 configuration lists a dependency on
gnome-speech-0.3.10.
> Is it actually using some feature of
gnome-speech-0.3.10 not present in
> 0.3.9? Or will it run just as well with the older
gnome-speech?

0.3.10 has needed fixes for the DECtalk and IBMTTS drivers. 
If you
don't care about these, then you can use a prior version.

> Error: Missing Dependency: eel > 2.14.0 is needed by
package orca
> Error: Missing Dependency: gnome-python2 >= 2.14.0
is needed by package orca
> Error: Missing Dependency: python(abi) = 2.4 is needed
by package orca
> Error: Missing Dependency: gnome-speech >= 0.3.10 is
needed by package orca
> Error: Missing Dependency: gtk+-2.0 >= 2.8.16 is
needed by package orcaError: Missing Dependency:
libnetsnmp.so.9 is needed by package kdeutils
> Error: Missing Dependency: libgtop-2.0.so.0 is needed
by package gnome-applets
> Error: Missing Dependency: libnetsnmp.so.9 is needed by
package openhpi
> Error: Missing Dependency: libnetsnmp.so.9 is needed by
package php-snmp
> Error: Missing Dependency: libgtop-2.0.so.0 is needed
by package gnome-python2-libgtop2

These dependencies are basically (I think) GNOME 2.14
components.  So,
hope things should work fine with Fedora Cora 5.  If this
isn't working
for you, let me know and we can start working through this. 
The
dependency list is something I'd like to narrow down and
simplify (e.g.,
I wish I could give a meta-dependency that encompasses a
cluster of
modules).

Will


_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

Hi, Willie:


I've cc'd Jonathan Blandford of Red Hat into this email,
because I think
Red Hat will want to bring out FC6 with Orca support. The
development
schedules I've seen mesh quite nicely.

In fact, it seems the currently shipping Open Office already
includes
the Michael Meeks direct AT-SPI to Uno bridge, if my reading
of the
Changelog is correct.

So ...

Willie Walker writes:
> Hi Janina:
> 
> > I've built an rpm for installing Orca 0.2.3 and
would be happy to make
> > it publically available,
> 
> Yeah!

For the record, anyone wanting this rpm can find it at:

ftp://ftp.SpeakupModified.Org/fedora/speakupmodified/current
/RPMS/

This address will persist. Exchange SRPMS for RPMS in the
above, and
you'll get the source rpm files. So, it's OK to
link/publish this
address. I'll track your .tar.gz releases at least, and
perhaps even
nightly CVS builds, if there's need for that.

I don't have to do anything special to build these. Your
spec.in file
did the magic from a ./configure. So, it was a trivial task
to build the
rpm.

I'm still working on the html page, but we'll also have
web access to
these files soon.

> 
> >  but it won't install as currently configured
> > for lack of 8 dependencies.
> 
> Darn!
> 
> >  These 8 dependency packages aren't even
> > available in the Fedora development repository
yet.
> 
> Are you using Fedora Core 5?  Because of the large
number of crasher and
> other bug fixes that went into GNOME 2.14 across a
number of GNOME
> components, we're now requiring GNOME 2.14, which I
think is what comes
> with Fedora Core 5.

Yes, FC5 here on all machines, and fully updated as of last
night.

> 
> > The orca-0.2.3 configuration lists a dependency on
gnome-speech-0.3.10.
> > Is it actually using some feature of
gnome-speech-0.3.10 not present in
> > 0.3.9? Or will it run just as well with the older
gnome-speech?
> 
> 0.3.10 has needed fixes for the DECtalk and IBMTTS
drivers.  If you
> don't care about these, then you can use a prior
version.

OK. I'll also build 0.3.10, as I am hoping to use ibmtts.
Indeed, I'm
working on making it generally available for purchase at
http://TTSynth.Com, but
we've been stuck for quite a few months for
various reasons.
> 
> > Error: Missing Dependency: eel > 2.14.0 is
needed by package orca
> > Error: Missing Dependency: gnome-python2 >=
2.14.0 is needed by package orca
> > Error: Missing Dependency: python(abi) = 2.4 is
needed by package orca
> > Error: Missing Dependency: gnome-speech >=
0.3.10 is needed by package orca
> > Error: Missing Dependency: gtk+-2.0 >= 2.8.16
is needed by package orcaError: Missing Dependency:
libnetsnmp.so.9 is needed by package kdeutils
> > Error: Missing Dependency: libgtop-2.0.so.0 is
needed by package gnome-applets
> > Error: Missing Dependency: libnetsnmp.so.9 is
needed by package openhpi
> > Error: Missing Dependency: libnetsnmp.so.9 is
needed by package php-snmp
> > Error: Missing Dependency: libgtop-2.0.so.0 is
needed by package gnome-python2-libgtop2
> 
> These dependencies are basically (I think) GNOME 2.14
components.  So,
> hope things should work fine with Fedora Cora 5.  If
this isn't working
> for you, let me know and we can start working through
this.  The
> dependency list is something I'd like to narrow down
and simplify (e.g.,
> I wish I could give a meta-dependency that encompasses
a cluster of
> modules).
> 

That's the main reason I've cc'd Jonathan into this
email. I'm hoping
he can help us track this better. I'd hate to build these
only to find
them showing up in the development repository a day later.
On the other
hand, I'm happy to build any that aren't likely to show up
there very
soon. So, it seems some coordination is the key.

And, there's a little good news since last night. The above
list of 8 is
now down to 5, as of about 30 minutes ago:

--> Finished Dependency Resolution
Error: Missing Dependency: eel > 2.14.0 is needed by
package orca
Error: Missing Dependency: gnome-python2 >= 2.14.0 is
needed by package
orca
Error: Missing Dependency: python(abi) = 2.4 is needed by
package orca
Error: Missing Dependency: gnome-speech >= 0.3.10 is
needed by package
orca
Error: Missing Dependency: gtk+-2.0 >= 2.8.16 is needed
by package orca


For the record, I'm attempting to install using yum as
follows:

yum --enablerepo=development upgrade ./orca-0.2.3-1.i386.rpm

This tells yum to look for dependencies in the Fedora
development
repositories. I'm saying "upgrade" rather than
"install" because I
already have orca-0.2.0 installed on this particular
machine.

Janina

> Will
> 
> 
> _______________________________________________
> Orca-list mailing list
> Orca-listgnome.org
> http
://mail.gnome.org/mailman/listinfo/orca-list

-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com

Marketing the Owasys 22C talking screenless cell phone in
the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janinafreestandards.org		http://a11y.org
_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

I have some progress to report but still need your help
figuring out
dependencies for FC5.

We reran the rpmbuild process having first commented out the
several
"requires" statements in the orca.spec file. We
left "buildrequires"
alone, of course.

This gave us a build that installed without complaint. We
then querried
the rpm to see what modules it used in the build and got:

#
[rootfantasia ~]# rpm -qRp orca-0.2.3-1.i386.rpm
/usr/bin/python
libc.so.6
libc.so.6(GLIBC_2.1.3)
libc.so.6(GLIBC_2.4)
libglib-2.0.so.0
python(abi) = 2.4
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1

To my amateur eye this suggests that the gnome-speech
requires statement
needs to go back into the spec file, but what about the
remaining
requires statements? What else is actually needed in runtime
that is not
automatically referenced during the build? For instance, it
seems the
gtk+ requirement is something of a misnomer in Fedora, as
gtk2-2.8.17-1.fc5.1 is actually installed. Ditto for eel and
python.

OK. I'm going to go build gnome-speech while I await your
advice.
Thanks, Willie.

PS: For easy reference, the spec file requires are listed as
follows:

Requires:       gtk+-2.0 >= 2.8.16
Requires:       atk >= 1.11.3
Requires:       gail >= 1.8.11
Requires:       libgail-gnome >= 1.1.3
Requires:       eel > 2.14.0
Requires:       at-spi >= 1.7.6
Requires:       gnome-speech >= 0.3.10
Requires:       python >= 2.4.0
Requires:       pyorbit >= 2.14.0
Requires:       pygtk2 >= 2.8.4
Requires:       gnome-python2 >= 2.14.0
Requires:       gnome-mag >= 0.12.0
Requires:       libbonobo >= 2.8.0
 
Janina


Janina Sajka writes:
> Hi, Willie:
> 
> 
> I've cc'd Jonathan Blandford of Red Hat into this
email, because I think
> Red Hat will want to bring out FC6 with Orca support.
The development
> schedules I've seen mesh quite nicely.
> 
> In fact, it seems the currently shipping Open Office
already includes
> the Michael Meeks direct AT-SPI to Uno bridge, if my
reading of the
> Changelog is correct.
> 
> So ...
> 
> Willie Walker writes:
> > Hi Janina:
> > 
> > > I've built an rpm for installing Orca 0.2.3
and would be happy to make
> > > it publically available,
> > 
> > Yeah!
> 
> For the record, anyone wanting this rpm can find it at:
> 
>
ftp://ftp.SpeakupModified.Org/fedora/speakupmodified/current
/RPMS/
> 
> This address will persist. Exchange SRPMS for RPMS in
the above, and
> you'll get the source rpm files. So, it's OK to
link/publish this
> address. I'll track your .tar.gz releases at least,
and perhaps even
> nightly CVS builds, if there's need for that.
> 
> I don't have to do anything special to build these.
Your spec.in file
> did the magic from a ./configure. So, it was a trivial
task to build the
> rpm.
> 
> I'm still working on the html page, but we'll also
have web access to
> these files soon.
> 
> > 
> > >  but it won't install as currently
configured
> > > for lack of 8 dependencies.
> > 
> > Darn!
> > 
> > >  These 8 dependency packages aren't even
> > > available in the Fedora development
repository yet.
> > 
> > Are you using Fedora Core 5?  Because of the large
number of crasher and
> > other bug fixes that went into GNOME 2.14 across a
number of GNOME
> > components, we're now requiring GNOME 2.14, which
I think is what comes
> > with Fedora Core 5.
> 
> Yes, FC5 here on all machines, and fully updated as of
last night.
> 
> > 
> > > The orca-0.2.3 configuration lists a
dependency on gnome-speech-0.3.10.
> > > Is it actually using some feature of
gnome-speech-0.3.10 not present in
> > > 0.3.9? Or will it run just as well with the
older gnome-speech?
> > 
> > 0.3.10 has needed fixes for the DECtalk and IBMTTS
drivers.  If you
> > don't care about these, then you can use a prior
version.
> 
> OK. I'll also build 0.3.10, as I am hoping to use
ibmtts. Indeed, I'm
> working on making it generally available for purchase
at
> http://TTSynth.Com,
but we've been stuck for quite a few months for
> various reasons.
> > 
> > > Error: Missing Dependency: eel > 2.14.0 is
needed by package orca
> > > Error: Missing Dependency: gnome-python2
>= 2.14.0 is needed by package orca
> > > Error: Missing Dependency: python(abi) = 2.4
is needed by package orca
> > > Error: Missing Dependency: gnome-speech >=
0.3.10 is needed by package orca
> > > Error: Missing Dependency: gtk+-2.0 >=
2.8.16 is needed by package orcaError: Missing Dependency:
libnetsnmp.so.9 is needed by package kdeutils
> > > Error: Missing Dependency: libgtop-2.0.so.0
is needed by package gnome-applets
> > > Error: Missing Dependency: libnetsnmp.so.9 is
needed by package openhpi
> > > Error: Missing Dependency: libnetsnmp.so.9 is
needed by package php-snmp
> > > Error: Missing Dependency: libgtop-2.0.so.0
is needed by package gnome-python2-libgtop2
> > 
> > These dependencies are basically (I think) GNOME
2.14 components.  So,
> > hope things should work fine with Fedora Cora 5. 
If this isn't working
> > for you, let me know and we can start working
through this.  The
> > dependency list is something I'd like to narrow
down and simplify (e.g.,
> > I wish I could give a meta-dependency that
encompasses a cluster of
> > modules).
> > 
> 
> That's the main reason I've cc'd Jonathan into this
email. I'm hoping
> he can help us track this better. I'd hate to build
these only to find
> them showing up in the development repository a day
later. On the other
> hand, I'm happy to build any that aren't likely to
show up there very
> soon. So, it seems some coordination is the key.
> 
> And, there's a little good news since last night. The
above list of 8 is
> now down to 5, as of about 30 minutes ago:
> 
> --> Finished Dependency Resolution
> Error: Missing Dependency: eel > 2.14.0 is needed by
package orca
> Error: Missing Dependency: gnome-python2 >= 2.14.0
is needed by package
> orca
> Error: Missing Dependency: python(abi) = 2.4 is needed
by package orca
> Error: Missing Dependency: gnome-speech >= 0.3.10 is
needed by package
> orca
> Error: Missing Dependency: gtk+-2.0 >= 2.8.16 is
needed by package orca
> 
> 
> For the record, I'm attempting to install using yum as
follows:
> 
> yum --enablerepo=development upgrade
./orca-0.2.3-1.i386.rpm
> 
> This tells yum to look for dependencies in the Fedora
development
> repositories. I'm saying "upgrade" rather
than "install" because I
> already have orca-0.2.0 installed on this particular
machine.
> 
> Janina
> 
> > Will
> > 
> > 
> > _______________________________________________
> > Orca-list mailing list
> > Orca-listgnome.org
> > http
://mail.gnome.org/mailman/listinfo/orca-list
> 
> -- 
> 
> Janina Sajka				Phone: +1.240.715.1272
> Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com
> 
> Marketing the Owasys 22C talking screenless cell phone
in the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.
> 
> Chair, Accessibility Workgroup		Free Standards Group
(FSG)
> janinafreestandards.org		http://a11y.org
> _______________________________________________
> Orca-list mailing list
> Orca-listgnome.org
> http
://mail.gnome.org/mailman/listinfo/orca-list

-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com

Marketing the Owasys 22C talking screenless cell phone in
the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janinafreestandards.org		http://a11y.org
_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

> This gave us a build that installed without complaint.
We then querried
> the rpm to see what modules it used in the build and
got:

Ahh - cool - didn't know it could do that.

> automatically referenced during the build? For
instance, it seems the
> gtk+ requirement is something of a misnomer in Fedora,
as
> gtk2-2.8.17-1.fc5.1 is actually installed. Ditto for
eel and python.

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.

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.

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.

Will


_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

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-listgnome.org
> http
://mail.gnome.org/mailman/listinfo/orca-list

-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com

Marketing the Owasys 22C talking screenless cell phone in
the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janinafreestandards.org		http://a11y.org
_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

One more thought ...

Janina Sajka writes:
> Willie Walker writes:
> 
> > 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.
> 
...
> to help with correct package identifiers. How easy is
it to get a list of
> what Orca actually needs at runtime?
> 
I think I can take the next cut at this as follows:

1.)	I will compare your list of requires against package
names
typically available on Fedora.

2.)	 I'll come back here with the diff, e.g. gtk+,

That should make it easier to figure out what in Fedora
provides the
missing pieces.

> Janina
> 
> > 
> > Will
> > 
> > 
> > _______________________________________________
> > Orca-list mailing list
> > Orca-listgnome.org
> > http
://mail.gnome.org/mailman/listinfo/orca-list
> 
> -- 
> 
> Janina Sajka				Phone: +1.240.715.1272
> Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com
> 
> Marketing the Owasys 22C talking screenless cell phone
in the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.
> 
> Chair, Accessibility Workgroup		Free Standards Group
(FSG)
> janinafreestandards.org		http://a11y.org
> _______________________________________________
> Orca-list mailing list
> Orca-listgnome.org
> http
://mail.gnome.org/mailman/listinfo/orca-list

-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com

Marketing the Owasys 22C talking screenless cell phone in
the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janinafreestandards.org		http://a11y.org
_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

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:

wwalkertecra:~/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-listgnome.org
> > http
://mail.gnome.org/mailman/listinfo/orca-list
> 

_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

Hi, Willie:

OK, I've taken all the 'requires' statements from the
orca.spec.in file
and checked against FC5, including the Fedora development
repositories.
It looks like there are three package discrepencies, my
second and third
categories below:

Dependencies Met or Exceeded:

	Requires:	atk >= 1.11.3
	Have atk-1.11.4-1.fc5.1

	Requires:	gail >= 1.8.11
	Have gail-1.8.11

	Requires:	libgail-gnome >= 1.1.3
	Have libgail-gnome-1.1.3-1.2

	Requires:	at-spi >= 1.7.6
	Have at-spi-1.7.7-6

	Requires:	gnome-speech >= 0.3.10
	Built and installed gnome-speech-0.3.10-1.0spk &
gnome-speech-ibmtts-0.3.10-1spk

	Requires:	python >= 2.4.0
	Have python-2.4.3-2

	Requires:	pyorbit >= 2.14.0
	Have pyorbit-2.14.0-1

	Requires:	pygtk2 >= 2.8.4
	Have pygtk2-2.8.6-0.fc5.1

	Requires:	gnome-mag >= 0.12.0
	Have gnome-mag-0.12.4-1

	Requires:	libbonobo >= 2.8.0
	Have libbonobo-2.14.0-1

Dependencies With Naming Conflicts:

	Requires:	gtk+-2.0 >= 2.8.16
	Instead, we have gtk2-2.8.17-2

	Requires:	eel > 2.14.0
	Instead, we have eel2-2.14.1-2


Can you name some of the modules provided by these two, so
we can double
check whether this really is just a package naming conflict?

Dependencies Not Met

	Requires:	gnome-python2 >= 2.14.0
	Have gnome-python2-2.12.4-1

There doesn't appear to be a 2.14 at ftp.gnome.org, only
2.12 and
2.15 (released April 23). Am I looking in the wrong place?

Thanks for your continued help on this, Willie.

-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://CapitalAccessi
bility.Com

Marketing the Owasys 22C talking screenless cell phone in
the U.S. and Canada--Go to http://ScreenlessPhone.Com
 to learn more.

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janinafreestandards.org		http://a11y.org
_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list

Hi Janina:

Here's the results of the pkg-config on the dependencies in
the new
orca.spec file I checked in yesterday.  I checked them on my
Solaris
machine:

pkg-config --modversion glib-2.0
2.10.1
pkg-config --modversion gtk+-2.0
2.8.16
pkg-config --modversion libbonobo-2.0
2.14.0
pkg-config --modversion atk
1.11.3
pkg-config --modversion gail
1.8.11
pkg-config --modversion eel-2.0
2.14.0
pkg-config --modversion libspi-1.0
1.7.6
pkg-config --modversion cspi-1.0
1.7.6
pkg-config --modversion gnome-speech-1.0
0.3.10

and my Ubuntu machine:

pkg-config --modversion glib-2.0
2.10.2
pkg-config --modversion gtk+-2.0
2.8.17
pkg-config --modversion libbonobo-2.0
2.14.0
pkg-config --modversion atk
1.11.4
pkg-config --modversion gail
1.8.11
pkg-config --modversion eel-2.0
2.14.1
pkg-config --modversion libspi-1.0
1.7.7
pkg-config --modversion cspi-1.0
1.7.7
pkg-config --modversion gnome-speech-1.0
0.4.0

There are still additional dependencies needed by Orca, but
I'm not sure
how to express them in the spec file or configure.in, except
as these
comments I've placed in configure.in to remind me:

# pyorbit 2.14.0
# pygtk 2.8.4
# gnome-python 2.6.2
# libgail-gnome 1.1.3
# gnome-mag-1.0 0.12.3 (optional)

Will

On Thu, 2006-05-04 at 19:01 -0400, Janina Sajka wrote:
> Hi, Willie:
> 
> OK, I've taken all the 'requires' statements from
the orca.spec.in file
> and checked against FC5, including the Fedora
development repositories.
> It looks like there are three package discrepencies, my
second and third
> categories below:
> 
> Dependencies Met or Exceeded:
> 
> 	Requires:	atk >= 1.11.3
> 	Have atk-1.11.4-1.fc5.1
> 
> 	Requires:	gail >= 1.8.11
> 	Have gail-1.8.11
> 
> 	Requires:	libgail-gnome >= 1.1.3
> 	Have libgail-gnome-1.1.3-1.2
> 
> 	Requires:	at-spi >= 1.7.6
> 	Have at-spi-1.7.7-6
> 
> 	Requires:	gnome-speech >= 0.3.10
> 	Built and installed gnome-speech-0.3.10-1.0spk &
gnome-speech-ibmtts-0.3.10-1spk
> 
> 	Requires:	python >= 2.4.0
> 	Have python-2.4.3-2
> 
> 	Requires:	pyorbit >= 2.14.0
> 	Have pyorbit-2.14.0-1
> 
> 	Requires:	pygtk2 >= 2.8.4
> 	Have pygtk2-2.8.6-0.fc5.1
> 
> 	Requires:	gnome-mag >= 0.12.0
> 	Have gnome-mag-0.12.4-1
> 
> 	Requires:	libbonobo >= 2.8.0
> 	Have libbonobo-2.14.0-1
> 
> Dependencies With Naming Conflicts:
> 
> 	Requires:	gtk+-2.0 >= 2.8.16
> 	Instead, we have gtk2-2.8.17-2
> 
> 	Requires:	eel > 2.14.0
> 	Instead, we have eel2-2.14.1-2
> 
> 
> Can you name some of the modules provided by these two,
so we can double
> check whether this really is just a package naming
conflict?
> 
> Dependencies Not Met
> 
> 	Requires:	gnome-python2 >= 2.14.0
> 	Have gnome-python2-2.12.4-1
> 
> There doesn't appear to be a 2.14 at ftp.gnome.org,
only 2.12 and
> 2.15 (released April 23). Am I looking in the wrong
place?
> 
> Thanks for your continued help on this, Willie.
> 

_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list