| 1 |
Derek Greentree wrote: |
| 2 |
> Hi all, |
| 3 |
> Basically, I'm trying to run and hack a python script that says things |
| 4 |
> like |
| 5 |
> "from gnome import *" |
| 6 |
> Now, there are 2 packages in portage, gnome-python and pygtk. They |
| 7 |
> seem to provide the same stuff in terms of the files they install: |
| 8 |
> what's the difference between these 2 packages. However, the big problem |
| 9 |
> is that even with either (or both) installed the said python script |
| 10 |
> doesn't work; I get this error: |
| 11 |
> |
| 12 |
> from gnome import * |
| 13 |
> ImportError: No module named gnome |
| 14 |
> |
| 15 |
> So, |
| 16 |
> 1. Are these two packages, gnome-python and pygtk, really different? |
| 17 |
> 2. What can I emerge (or what do I need to make an ebuild for) so that |
| 18 |
> a python script can do an "import gnome"? |
| 19 |
> |
| 20 |
|
| 21 |
Hi, |
| 22 |
|
| 23 |
i ran into this odd couple as well. It seems gnome-python provides |
| 24 |
everything pygtk provides (altough i didn't have a good look), but since |
| 25 |
there might be apps that use only pygtk stuff and don't need all the |
| 26 |
dependencies that come with gnome-python (all sorts of gnome stuff) it |
| 27 |
is logical to provide them both (altough portage wasn't mean for this |
| 28 |
sort of situations afaik). |
| 29 |
|
| 30 |
Now, the only problems i ran into was with the Gnome2 pygtk ebuild |
| 31 |
(1.99), with the old one (0.6.8) everything should be fine. The 1.99 |
| 32 |
version overwrites part of the old gnome-python package resulting in |
| 33 |
some weird problems. You might try uninstalling it all and then just |
| 34 |
installing gnome-python and maybe (if needed after all) the gnome1 pygtk |
| 35 |
build (0.6.8). |
| 36 |
|
| 37 |
- fos |
Archives