[MacPorts] #31464: beanstalkd: remove redundant launchd instructions

[MacPorts]

#31464: beanstalkd: remove redundant launchd instructions
-------------------------------------+--------------------------------------
 Reporter:  ryandesign@…             |       Owner:  nick@…           
     Type:  defect                   |      Status:  new              
 Priority:  Normal                   |   Milestone:                   
Component:  ports                    |     Version:  2.0.3            
 Keywords:  haspatch                 |        Port:  beanstalkd       
-------------------------------------+--------------------------------------
 Installing beanstalkd looks like this:

 {{{
 --->  Fetching beanstalkd
 --->  Attempting to fetch beanstalkd-1.4.6.tar.gz from
 http://xph.us/dist/beanstalkd/
 --->  Verifying checksum(s) for beanstalkd
 --->  Extracting beanstalkd
 --->  Applying patches to beanstalkd
 --->  Configuring beanstalkd
 --->  Building beanstalkd
 --->  Staging beanstalkd into destroot
 --->  Creating launchd control script
 ###########################################################
 # A startup item has been generated that will aid in
 # starting beanstalkd with launchd. It is disabled
 # by default. Execute the following command to start it,
 # and to cause it to launch at startup:
 #
 # sudo port load beanstalkd
 ###########################################################
 --->  Installing beanstalkd @1.4.6_2+universal
 --->  Activating beanstalkd @1.4.6_2+universal
 ###########################################################
 # To launch beanstalkd manually, run:
 #
 # sudo launchctl load -w
 /Library/LaunchDaemons/org.macports.beanstalkd.plist
 #
 # and to stop beanstalkd, run:
 #
 # sudo launchctl unload -w
 /Library/LaunchDaemons/org.macports.beanstalkd.plist
 ###########################################################
 --->  Cleaning beanstalkd
 }}}

 As you see, instructions for how to start beanstalkd are printed twice:
 once by MacPorts base, and a second time by the port itself. The solution
 is to remove the post-activate block in the port and just let MacPorts
 print the message.

-- 
Ticket URL: <https://trac.macports.org/ticket/31464>
MacPorts <http://www.macports.org/>
Ports system for Mac OS