Maybe this doesn't belong on this list, but what's the motivation behind installing all of mailman into it's own heirarchy? I'd think that it would be much more "FHS Compliant" to break things up and put them throughout the filesystem where they "belong". Any decent package management system should be able to keep track of where files are installed, and that's the only good motivation that I can think of for putting mailman on its own.

I'd like to second this statement. fhs compliance would be a plus - or at least ease of configuration to fhs compliance. It would make rpm and deb building MUCH easier. instead of symlinking everywhere.

-sv

Maybe this doesn't belong on this list, but what's the motivation behind installing all of mailman into it's own heirarchy? I'd think that it would be much more "FHS Compliant" to break things up and put them throughout the filesystem where they "belong". Any decent package management system should be able to keep track of where files are installed, and that's the only good motivation that I can think of for putting mailman on its own.

I'd like to second this statement. fhs compliance would be a plus - or at least ease of configuration to fhs compliance. It would make rpm and deb building MUCH easier. instead of symlinking everywhere.

-sv