Mailinglist Archive: opensuse (4288 mails)

[Brian Durant <durant@xxxxxxxxxx>]

On Sunday 26 May 2002 18:43, John Lamb wrote:
- Start YaST->Install Software,
-
- Search for gimp and include package descriptions. Make sure you have
- gimp-devel
- and
- gtk-devel
- installed
- That ought to sort out any gimptool problems. It worked for me.

Nice to hear from you again John. YES <LOL>. That did it for gimptool. 
However, I still got the PDF and HTML package errors:

checking for dvips... no
configure: WARNING: PostScript documentation cannot be regenerated!
checking for db2pdf... no
configure: WARNING: PDF user's guide cannot be regenerated!
checking for dvipdf... /usr/bin/dvipdf
checking for db2ps... no
configure: WARNING: PostScript user's guide cannot be regenerated!
checking for db2html... no
configure: WARNING: HTML user's guide cannot be regenerated!


Will this affect the "make" and "make install"?? I assume that this will only 
affect the user guide, but it would still be nice to have it. Otherwise I 
will be just as blind (or more) than I have been so far 8-)

- A similar process often works for other missing packages where you know
- the name only of one executable, e.g. db2ps. However, a lot of the SuSE
- rpms contain a collection of executables and don't list all in the
- package description. In that case, you may be able to search with
- System->Configuration->KPackage or hunt through the packages on the
- CD-ROM using
- # rpm -qpi --provides *.rpm | less
-
- *The package for db2pdf is called docbook-toys.*

Two problems here:

1) I can't figure out how to get a pipe "|" on my Danish keyboard. Any Danes 
on the list that can help me out here?

2) docbook-toys isn't listed under YAST 2 with SuSE 7.3 Pro.

-
- Perhaps someone else can suggest a better way of searching for packages.
-
- Unfortunately, hunting for packages is an inevitable consequence of
- trying to compile a package yourself. If you're going to do this more
- often, it's wise to have lots of *-devel packages installed. These
- typically contain the *.h files needed to use libraries you want to link
- against.

Thanks for the advice. Hopefuly I won't have to do so much of that.

Cheers,

Brian