[91233] trunk/dports/databases/mysql55/Portfile
Bradley Giesbrecht
pixilla at macports.org
Tue Mar 27 08:12:33 PDT 2012
On Mar 27, 2012, at 3:46 AM, Rainer Müller wrote:
> On 03/27/2012 02:49 AM, Ryan Schmidt wrote:
>>> Modified: trunk/dports/databases/mysql55/Portfile
>>> ===================================================================
>>> --- trunk/dports/databases/mysql55/Portfile 2012-03-26 15:08:04 UTC (rev 91232)
>>> +++ trunk/dports/databases/mysql55/Portfile 2012-03-26 15:24:06 UTC (rev 91233)
>>> @@ -13,7 +13,7 @@
>>> platforms darwin
>>> maintainers pixilla openmaintainer
>>>
>>> -subport mysql55 {
>>> +if {$subport == $name} {
>>
>> So wait, this actually causes a problem? That's unfortunate, and it means I have several places where I need to undo this.
>
> I think the current terminology means that if $subport equals $name,
> then this is should not be a subport at all, but the "main" port. For
> this mysql55 port, the subports mysql55 and mysql55-server are quite
> different and probably should not be implemented as a subport.
Adding mysql55-server as a subport has the convenience of keeping the
version in sync with mysql55. Like most of the *-server ports the
mysql55-server will rarely if ever require updating.
Should I make the mysql55-server port an independent port and make
the version a very different number than the mysql55 version, a date string
for example?
My reason for keeping the mysql55 and mysql55-server versions in sync is
to avoid confusion. Making the version very different may attain the same
result.
Regards,
Bradley Giesbrecht (pixilla)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2763 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20120327/447d04cb/attachment.bin>
More information about the macports-dev
mailing list