Hi there! I was having a good time with v 10.0 RC1 this weekend (the installation went flawless) until I started to look for packages I had in 9.3 but could not find in 10.0 RC1, then I ran into issues. I could not find several of the perl-xxx.rpm packages (I don't have the complete list with me but included things like perl-HTML-Mason-xxx.rpm, perl-SQL-xxx.rpm). Then I went to "www.opensuse.org/download" and tried to get the source - I was fine, downloaded the source and installed the binary rpm's from there. I don't know how to do this with yast so I ran rpm commands. I found several packages were missing such as gd-devel-xxx, pwlist-devel-xxx and a postregsql-devel from source. My question: doesn't it make sense to create the binary rpm's once the source is available for the distro? One of the source-rpm forced me to download 10 other packages before it would compile and install the binary rpm's. One of those packages requested gd-devel-xxx.rpm which I could just not find anywhere in either source or binary so I haven't been able to install the binary-rpm. Another question, I use Apache-1.3 and mod_perl 1.2 since apache2 with mod_perl and mason is not really ready for prime time (besides, I tried to make mason play with apache2 and after 12 hours of work gave up). Why is it that there is no RPM version available for SUSE? I have a source-RPM but I got if from RedHat. It might work but I have not tried. Regards, Uriel_Carrasquilla@ncci.com NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.