Scalix Forums

dear all.

I have just installed an evaluation version of Scalix 9 on SuSE 9.0.

Noticed that in the list of package requirements it says:

"... all platforms require: ... textutils, fileutils, sh-utils". I cannot locate these packages on my suse system. (yast, software, install and remove software, search for package, en then search for these utilities)

It seems that this has to be adjusted for SuSE? Previously I also installed on RedHat, and could install these packages there without problem.

Maybe it's an idea to add Python to system requirements..? As you need that to be able to install the scalix configuration script... (so basically it is a system requirement, isn't it?)

Hi,

When you ran your installation, did RPM complain about any missing packages ?

It seems that this has to be adjusted for SuSE?

What adjustments did you need to make ?

I take your point about Python. I'll check over the documentation to see if it's mentioned anywhere else. It's not actually a requirement for any of the scalix-server RPMs, it's required for SWA or our administration console. Neither of those components are mandatory.

Cheers

Dave Kelly
Senior Support Engineer
Scalix Corporation

rpm did not complain, no.

but still, in the docs it says there packages are required for all platforms: textutils, fileutils and sh-utils. Yet, in SuSE, these packages do not exist. (at least: I can't find them)

so, even though rpm did not complain, I was unable to check wether the required packages were installed or not...

yours,
mj

Well...you learn a new thing every day :-)

I found a magic invocation of rpm that shows us what package provides the ones we're looking for.

A standard rpm -q --provides doesn't give us the details because textutils et al. is provided by another package, coreutils.

This can be seen by running

rpm -q --whatprovides textutils

Cheers

Dave.

ScalixSupport wrote:Well...you learn a new thing every day :-)

rpm -q --whatprovides textutils

thanks very much.

instead of using the rpm command line, I used yast to select the packages.

I guess there's nothing that beats the good old command line stuff :)

anyway, thanks.

oh, and more thing. When I follow installation instructions, I'm told to do:
export PATH=$PATH:/opt/scalix/bin

It does not say to make this permanent, so after the first reboot, I had various problems that were solved after changing the path. this might be very obvious for you guru's, but not for someone like me :)

Anyway, thanks for having taken the time to read and reply.

mj