CommuniGatePro is an MTA, IMAP(S), POP3(S),WebMail,... server From the Homepage: The leading high-end Internet Messaging platform, CommuniGate Pro has set a new industry standard in scalability and reliability. Effective design allows CommuniGate Pro to support more features, consume less resources, and require less maintenance than any other product on the market today. The license is commercial, stalker allowed automatic download ebuild: It's your program, so you are free to do whatever you want with it. If it does not contain our software (but just downloads it from our web/ftp sites), then it's OK with us. A lot of ppl were installing that app with rpm --nodeps, should do better with ebuild :) init/conf script is available. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 32888 [details] the ebuild(s) + scripts i suggest net-mail as category
Uhm..., my 2 cents :) 1. Attached your ebuild, supported files as plain text. 2. IMHO, build from source is preferred: http://www.stalker.com/pub/CommuniGatePro/CGatePro-Linux-Intel.tgz . 3. KEYWORDS="~x86". 4. CGP provides virtual/mta, virtual/mda, virtual/imapd. 5. Required optional mailwrapper support (please take a look at ebuilds in mail-mta) 6. RDEPEND to block other virtual/mta. I've been using CGP under Win32. It is a very good packages and easy to configure.
Created attachment 32922 [details] communigatepro-4.1.8.ebuild
Created attachment 32923 [details] communigate.conf please put in files/script
Created attachment 32924 [details] communigate.init please put in files/script
1 -> done 2 -> no good idea. this points to the latest rlz and tis will break md5 after they update 3 -> didn't do this, 4.1.8 is stable, 4.2.3b is beta. mark 4.1.8 as unstable if you thing its needed 4. -> done 5. -> done (I hope correctly) 6. -> done (I thing)
concerning item number 3, all ebuilds are to be marked unstable(this is seperate from the stability of the actual program) until they are tested and working in portage. Please read up on the gentoo ebuild policies for more clarification. Besides that, thanks for the ebuild, ill test and report back later this evening.
Maybe it's a good idea to add $base_dir="/opt/CommuniGate" to communigate.conf and modify communigate.init --Base /opt/CommuniGate to --Base $base_dir in start() and controller() :)
Created attachment 39927 [details] communigatepro-4.2.2.ebuild ebuild the actual ebuild
Created attachment 39928 [details] communigate.conf in files/script the config file for the initscript
Created attachment 39929 [details] communigate.init the init script the init script to make everything complete
seems no-one interested yet in 3 years -> wontfix reopen and join us in #gentoo-sunrise if you feel otherwise
