[MacPorts] #33226: omniORB @4.1.6 +python27 New upstream version and python version

[MacPorts]

#33226: omniORB @4.1.6 +python27 New upstream version and python version
------------------------------------+---------------------------------------
 Reporter:  lockhart@…              |       Owner:  stromnov@…           
     Type:  update                  |      Status:  new                  
 Priority:  Normal                  |   Milestone:                       
Component:  ports                   |     Version:  2.0.3                
 Keywords:  haspatch                |        Port:  omniORB              
------------------------------------+---------------------------------------

Comment(by cal@…):

 Replying to [comment:3 lockhart@…]:
 > OK, thanks for the feedback. How are ports updated for new upstream
 versions? Is opening a ticket like this the right way to do it? 4.1.6 has
 been available since 2011-07-01 and it would be nice to stay current with
 what is available.

 Yes, that's the way we usually take if the maintainer doesn't update the
 port or there is no maintainer.

 >I'll look at making the compiler choice conditional and post new patches,
 and carry along my own local ports repository to allow more testing. More
 feedback and direction is welcome.

 You're on the right way, if you implemented the compiler change pattern
 Ryan mentioned your patch should be ready for committing. Btw, if you
 attach a patch feel free to add "haspatch" to keywords. Also we usually cc
 or assign to the maintainer if there is any. There's no need to cc
 yourself, because the reporter is always cc'ed (we're not the debian
 bugtracker here…) and the milestone field is only really interesting for
 bugs against base, because there is only one version of the ports tree and
 it's being upgraded in a rolling release fashion.

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