Autopackage install attempt with Inkscape on SuSE
![](https://secure.gravatar.com/avatar/8d5128b5b838ecedc34635fba7995f7f.jpg?s=120&d=mm&r=g)
Hi Guys,
Carl and I just tried out installation of Inkscape onto his SuSE 9.x box using autopackage, but ran into a dependency issue for "GTK 2 C++ bindings". I'm assuming that is the gtkmm2 package. It said that this would need to be installed manually, however we couldn't find what package this corresponds to for SuSE (looking at YaST and rpmfind.net.)
Do you have a suggestion for where we can find this package? Also, it would be nice if the GUI gave some directions to look when it fails to find a dependency.
Fwiw, we also had to use the `xhost +` trick to be able to see the GUI.
Thanks, Bryce
![](https://secure.gravatar.com/avatar/8d5128b5b838ecedc34635fba7995f7f.jpg?s=120&d=mm&r=g)
On Mon, 21 Jun 2004, Bryce Harrington wrote:
Hi Guys,
Carl and I just tried out installation of Inkscape onto his SuSE 9.x box using autopackage, but ran into a dependency issue for "GTK 2 C++ bindings". I'm assuming that is the gtkmm2 package. It said that this would need to be installed manually, however we couldn't find what package this corresponds to for SuSE (looking at YaST and rpmfind.net.)
Do you have a suggestion for where we can find this package? Also, it would be nice if the GUI gave some directions to look when it fails to find a dependency.
Btw, we tried the redhat 9 rpm's for gtkmm2, but they had half a dozen dependency issues for perl and some other base libs, so didn't look feasible.
Also, I re-ran the installer on my own system (which I had successfully installed with autopackage previously), and it installed without trouble. I didn't have to install gtkmm2 myself as far as I remember.
$ rpm -qa | grep gtkmm gtkmm-1.2.10-143 gtkmm-devel-1.2.10-143 $
Bryce
![](https://secure.gravatar.com/avatar/51fad6a48ab081e68329c2bd3e917894.jpg?s=120&d=mm&r=g)
Hi,
I'm assuming that is the gtkmm2 package. It said that this would need to be installed manually, however we couldn't find what package this corresponds to for SuSE (looking at YaST and rpmfind.net.) Do you have a suggestion for where we can find this package?
Have you tried rpmseek.com ?
Arpad Biro
__________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail
![](https://secure.gravatar.com/avatar/58a5209b61cc09379468fe48275f2ddf.jpg?s=120&d=mm&r=g)
On Mon, 2004-06-21 at 11:33 -0700, Bryce Harrington wrote:
Carl and I just tried out installation of Inkscape onto his SuSE 9.x box using autopackage, but ran into a dependency issue for "GTK 2 C++ bindings". I'm assuming that is the gtkmm2 package. It said that this would need to be installed manually, however we couldn't find what package this corresponds to for SuSE (looking at YaST and rpmfind.net.)
This should have worked, GTKmm2 and libsigc++ are packaged alongside inkscape itself, see the directory listing here:
http://navi.cx/~mike/inkscape/
Could you send me a DEBUGLEVEL=3 log? I guess for some reason we are not connecting to navi right or something ...
Do you have a suggestion for where we can find this package? Also, it would be nice if the GUI gave some directions to look when it fails to find a dependency.
You can install it directly from above, if you want. Yes I agree it would be nice if it gave the user directions. The problem is, how do we know where to find it? In future this stuff will be a part of the skeleton metadata but only because we need it to be able to resolve packages from the native distro repositories.
Fwiw, we also had to use the `xhost +` trick to be able to see the GUI.
Yes this is fixed in CVS.
thanks -mike
![](https://secure.gravatar.com/avatar/8d5128b5b838ecedc34635fba7995f7f.jpg?s=120&d=mm&r=g)
On Mon, 21 Jun 2004, Mike Hearn wrote:
On Mon, 2004-06-21 at 11:33 -0700, Bryce Harrington wrote:
Carl and I just tried out installation of Inkscape onto his SuSE 9.x box using autopackage, but ran into a dependency issue for "GTK 2 C++ bindings". I'm assuming that is the gtkmm2 package. It said that this would need to be installed manually, however we couldn't find what package this corresponds to for SuSE (looking at YaST and rpmfind.net.)
This should have worked, GTKmm2 and libsigc++ are packaged alongside inkscape itself, see the directory listing here:
http://navi.cx/~mike/inkscape/
Could you send me a DEBUGLEVEL=3 log? I guess for some reason we are not connecting to navi right or something ...
Okay, thanks, we'll give that a shot.
Do you have a suggestion for where we can find this package? Also, it would be nice if the GUI gave some directions to look when it fails to find a dependency.
You can install it directly from above, if you want. Yes I agree it would be nice if it gave the user directions. The problem is, how do we know where to find it? In future this stuff will be a part of the skeleton metadata but only because we need it to be able to resolve packages from the native distro repositories.
I would suggest perhaps indicating that the user may need to use their normal installation mechanism (i.e. YaST, rpmfind.net, etc.) Also, if it is possible to give a clue what the package name would be (i.e., 'Look for a package named something like libgtkmm2-* or gtkmm2-*'.) I think giving a few hints would make the error situation seem less "abrupt", and help ease the user over to traditional mechanisms. Or on the other hand, if it is to be considered a bug, perhaps provide an address for reporting bugs (i.e., this list if it's an autopackage issue, or the product's bug tracker URL otherwise.)
Bryce
![](https://secure.gravatar.com/avatar/58a5209b61cc09379468fe48275f2ddf.jpg?s=120&d=mm&r=g)
On Mon, 2004-06-21 at 13:15 -0700, Bryce Harrington wrote:
I would suggest perhaps indicating that the user may need to use their normal installation mechanism (i.e. YaST, rpmfind.net, etc.) Also, if it is possible to give a clue what the package name would be (i.e., 'Look for a package named something like libgtkmm2-* or gtkmm2-*'.) I think giving a few hints would make the error situation seem less "abrupt", and help ease the user over to traditional mechanisms. Or on the other hand, if it is to be considered a bug, perhaps provide an address for reporting bugs (i.e., this list if it's an autopackage issue, or the product's bug tracker URL otherwise.)
These are all good suggestions, and I've added them to the TODO list.
thanks -mike
participants (3)
-
Arpad Biro
-
Bryce Harrington
-
Mike Hearn