MySQL Bugs: #71541: Please package MEM in native package formats such as rpm

Bug #71541	Please package MEM in native package formats such as rpm
Submitted:	31 Jan 2014 9:54	Modified:	31 Jan 2014 11:09
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor	Severity:	S4 (Feature request)
Version:	3.0.5	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	windmill

Description:
MEM is packaged with special binary installers.
For those of us used to using a native package manager it's much more convenient to use rpms on RHEL/OEL and derived systems.  This fits in better with system deployment procedures.

How to repeat:
Download binaries for MEM and notice they are not native for the platform.

Suggested fix:
Oracle provides a lot of it's MySQL related software now in rpm format and using a yum repo.

Please consider doing the same for MEM.

Verifying.

For clarification it would be good to state whether it is the agent, service manager, or both that is most important to you here.

If we use a native package manager then it makes sense to package all components.
Compare with MySQL: there is a MySQL-server, MySQL-client, MySQL-shared-compat etc...

So I think it works for both sides. If the priority has to be assigned then it's clear that usually you expect the MEM server to service "n" MySQL servers, where "n" > 1 so it's likely that we'll be installing more agents than mem servers.

That said it seems that Oracle is growing in experience in packaging parts of the MySQL environment on rpm based systems so this is just a logical extension of that and makes life easier for us all.

Extending this to other major Linux packaging environments (I guess Debian's apt) makes sense if the number of users justifies this.

So I'm not expecting miracles but it would certainly be a nice to have, in my case first for the agent and second for the MEM server on rpm based systems. (RHEL 5, 6 or clones to start with).

I believe this is a duplicate of Bug #60832