[91233] trunk/dports/databases/mysql55/Portfile

[Rainer Müller]

On 03/27/2012 05:24 PM, Ryan Schmidt wrote:
> On Mar 27, 2012, at 08:00, Joshua Root wrote:
>> I never imagined that someone would write "subport foo" when they are
>> already defining the foo port outside of any subport block.
> 
> No, outside of any subport block, they're defining global things shared by all subports.

But this also defines a port... Otherwise we would be required to have
at least one subport. An alternative would be to imply an empty "subport
$name {}" construct if it is not given in the Portfile and handle all
ports as subport.

> Again, what actual problem does writing e.g. "subport mysql55" in the mysql55 port cause? As I said, I'm already doing this in several other ports and was not aware this caused any problem.

The mysql55-server port was not in the PortIndex.

However, I have not tracked down why defining a subport with the same
name as the port causes problems. I trust Joshua on this issue that it
is not going to work this way.

Rainer