Mads Martin Joergensen wrote:
* Tom Allison
[Nov 09. 2003 00:50]: I copied in to a directory every single rpm it was asking for and when I run:
current directory == /usr/src/dovecot/ build --clean --verify --rpms /usr/src/dovecot/
I get and error that it cannot find aaa_base.rpm Well, I'm looking at it and it's there.
What went wrong? What needs to be fixed?
Did you read the man-page to build before starting? First off you don't want to be in /usr/src/dovecot when calling build. You want to be in the directory with the package you want to build.
Also you might try
$ export BUILD_RPMS=/usr/src/dovecot/
and then
$ build --clean --verify
No need for the --rpms swich.
According to the man page export BUILD_RPMS=/usr/src/dovecot/ --rpms /usr/src/dovecot/ are synonymous. I am using 8.2 Professional fully updated from Suse websites. I selected 'build' over RPM because it seemed a better approach if I intended to build an rpm specifically for SuSE 8.2 that might be suitable for distribution to others. However, reading your continued threads about how 'build' is essentially farked in 8.2 and 9.0 (with some contention as to the exact farkiness therein/thereof/whatever) I'm just a wee bit disappointed. I am very favorably impressed with how well SuSE can get up and running as a desktop workstation. As far as the various comments people have about Linux != workstation environment they need to spend a few days with SuSE. However... My experience has led me to the conclusion that SuSE comes with a huge caveat. "Don't leave the path". For whatever it's worth, everything that I have done which is outside of the DEFAULT installation has been met with some level of limited success. I've been very careful to determine the exact area of shortcoming and to provide feedback as accurate as possible to SuSE. A specific example that really caught my by surprise was this: squirrelmail -- documentation (README.Suse) states that squirrelmail is intended for use with the imap (Univ. Wash) package. imap is compiled without imap support. It will only support imap-ssl protocol. squirrelmail, as shipped from Suse is version 1.2 and is incapable of imap-ssl support. This functionality was not available until 1.4 according the the squirrelmail mailing list. This, combined with the issues identified with 'build' lead me to conclude that SuSE, while having an excellent desktop environment, has limited capabilities for doing much on the Server side and even less when you attempt to do anything that is even more deviated from "The Path". Don't get me wrong, I'm not down on Suse. In fact I intend on keeping it as my desktop. But it's been a devil of a time getting the server working. There's been additional problems with cyrus-imap, cyrus-sasl, several other build packages (courier-imap is one), sieveshell authentication, ldap-anything (but that's likely my fault). But, I did get KDE's CD-burner working the first time I tried to use it. That was "cool".