1 |
Anthony Gorecki wrote: |
2 |
> On Wednesday, April 05, 2006 16:08, m h wrote: |
3 |
> |
4 |
>> My question is how do other packages that build against a slotted |
5 |
>> library know where to find the library? |
6 |
>> |
7 |
> Generally, there is no need to do that in an ebuild. The software package's |
8 |
> configure script will automatically run pkg-config in order to determine |
9 |
> which flags must be passed to the linker. (Assuming that you are referring to |
10 |
> an application which is written in a variant of C.) |
11 |
> |
12 |
> |
13 |
I've run across a similar issue in creating an ebuild for CastPodder. |
14 |
CastPodder is a python |
15 |
application that uses wxpython and pygtk. Currently CastPodder only |
16 |
works with Python 2.4 and requires |
17 |
the same major/minor version of wxpython and pygtk. I've set: |
18 |
|
19 |
|
20 |
DEPEND="=dev-lang/python-2.4* |
21 |
=dev-python/wxpython-2.4* |
22 |
>dev-python/pyxmms-2.0 |
23 |
=dev-python/pygtk-2.4*" |
24 |
|
25 |
to attempt to handle this dependency. On my x86 system, I have slotted |
26 |
install of: |
27 |
|
28 |
* dev-python/wxpython |
29 |
Available versions: 2.4.2.4 2.4.2.4-r3 ~2.6.0.0-r1 2.6.1.0 |
30 |
Installed: 2.4.2.4-r3 2.6.1.0 |
31 |
|
32 |
Now when CastPodder is ran, it is reporting: |
33 |
|
34 |
/usr/lib/python2.4/site-packages/wx-2.6-gtk2-unicode/wx/_core.py:13155: |
35 |
UserWarning: wxPython/wxWidgets release number mismatch |
36 |
warnings.warn("wxPython/wxWidgets release number mismatch") |
37 |
|
38 |
Notice that it is using wxpython-2.6 instead of 2.4. Any ideas on how I |
39 |
can more explicitly specify |
40 |
the 2.4 slot? |
41 |
|
42 |
TIA, |
43 |
Roy |
44 |
-- |
45 |
gentoo-dev@g.o mailing list |