Am 11.04.2011 21:09, schrieb Ben Eisenbraun:
On Mon, Apr 11, 2011 at 08:46:36PM +0200, Kay Diederichs wrote:

<110 lines elided>

I'm a big fan of KISS - my translation would be "keep it simple and
standard". The KISS principle states that simplicity should be a key
goal in design, and that unnecessary complexity should be avoided (from
Wikipedia).

The problem is that developers can't control how their software will be
deployed, especially in the case where the packaging is a simple tarball.
Since that's the case, wouldn't it be better to build a package that runs
unmodified on as many systems as possible?

And if that's the goal and the libgomp.so.3 that's distributed with Coot is
not compatible with SELinux, then shouldn't it be fixed _for everyone_ on
the build system side of things?*

Any solution where the user has to modify the downloaded package in order
to run it on their system can not be considered KISS.  It might be less
work than reporting the problem to the maintainers, so it might pass the
"simple" sniff test, but definitely not the "standard" one.

Alternately Paul could just put a note in the docs that says "Coot is not
compatible with SELinux" and leave it at that.

-ben

* Note that I don't use SELinux so I have no idea how accurate this is.


Ben,

all I can say is that on CentOS-5 one needs no "execstack" command run by root - it "just works".

My "KISS" comment was meant to be helpful wrt the question of root priviliges - some people may not realize that root privs are usually not required at all for installing and running a program.

If there were a magic wand to make a single coot tarball work on all distros then I'm sure Paul and Co would wave it. In its absence, users can only try and install the "closest" tarball and make it work somehow (and it's surely safer to rm some of the files than to run execstack as root), or they have to build from source.

BTW even the icc and ifort compilers provided by Intel are not fully compatible with SELinux! Nevertheless I use them all the time on my machines (hint:"setenforce 0" before, and "setenforce 1" after their installation).

Whether SELinux is a good thing or not is probably not a topic for the coot mailing list. But it's the default for RedHat's FC and RHEL so we'll have to get along with it.

best,

Kay

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to