RE: [Mailman-Users] Installation Issue
-----Original Message----- From: J C Lawrence [mailto:claw@cp.net] Sent: Monday, May 08, 2000 5:37 PM To: David Smead Cc: BCSi; mailman-users@python.org Subject: Re: [Mailman-Users] Installation Issue
On Mon, 8 May 2000 17:30:51 -0700 (PDT) David Smead <smead@amplepower.com> wrote:
On a Linux system, this will typically be /home/mailman.
This is a dangerous assumption based on the same (arguably ill advised) precepts that sadly gave us /home/httpd and co. For me $PREFIX ends up being /var/lib as that seems the most sensical given the purpose of the directory heirarchy and the FHS.
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. Greg
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
participants (2)
-
Gregory Leblanc -
Seth Vidal