Re: [109460] trunk/dports/security/certsync/Portfile

2013-08-15 Thread Joshua Root
On 2013-8-16 08:15 , Daniel J. Luke wrote:
> On Aug 15, 2013, at 6:09 PM, Joshua Root  wrote:
>>> Revision: 109460
>>>  https://trac.macports.org/changeset/109460
>>> Author:   landonf at macports.org
>>> Date: 2013-08-15 15:01:38 -0700 (Thu, 15 Aug 2013)
>>> Log Message:
>>> ---
>>> Enable 10.5 as a minimum target version
>>>
>>> Modified Paths:
>>> --
>>>trunk/dports/security/certsync/Portfile
>>>
>>> Modified: trunk/dports/security/certsync/Portfile
>>> ===
>>> --- trunk/dports/security/certsync/Portfile 2013-08-15 21:57:55 UTC (rev 
>>> 109459)
>>> +++ trunk/dports/security/certsync/Portfile 2013-08-15 22:01:38 UTC (rev 
>>> 109460)
>>> @@ -38,7 +38,7 @@
>>> build {
>>> system -W ${worksrcpath} "${configure.objc} \
>>> ${configure.objcflags} \
>>> -   -mmacosx-version-min=10.6 \
>>> +   -mmacosx-version-min=10.5 \
>>
>> Shouldn't this be using $macosx_deployment_target?
>>
>> And presumably this means that the code doesn't work on 10.4, so other
>> ports shouldn't depend on certsync on 10.4?
> 
> 
> do we care about 10.4 (I don't think we should). The only reason why it's a 
> little bit reasonable to care about 10.5 is that it's the last release that 
> runs on ppc machines.
> 
> In both cases, Apple isn't releasing updates for them anymore...

Sure, everything < 10.6 is nominally unsupported. Base still works back
to 10.4 and some maintainers choose to support those versions.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: [109460] trunk/dports/security/certsync/Portfile

2013-08-15 Thread Craig Treleaven
until the next generation MacBook Pros are announced, which I'm 
hoping is on September 10th.


I think the chances of that are slim to none.  Doesn't make sense for 
Apple to 'dilute' an iPhone event with Mac announcements.


Craig
(Not that I have any inside information.)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: [109460] trunk/dports/security/certsync/Portfile

2013-08-15 Thread Blair Zajac

On 08/15/2013 03:15 PM, Daniel J. Luke wrote:

do we care about 10.4 (I don't think we should). The only reason why it's a 
little bit reasonable to care about 10.5 is that it's the last release that 
runs on ppc machines.


Yes, please, our 5 year iMac went belly up so all I'm left with is our 
PPC PowerBook until the next generation MacBook Pros are announced, 
which I'm hoping is on September 10th.


Blair


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: [109460] trunk/dports/security/certsync/Portfile

2013-08-15 Thread Daniel J. Luke
On Aug 15, 2013, at 6:09 PM, Joshua Root  wrote:
>> Revision: 109460
>>  https://trac.macports.org/changeset/109460
>> Author:   landonf at macports.org
>> Date: 2013-08-15 15:01:38 -0700 (Thu, 15 Aug 2013)
>> Log Message:
>> ---
>> Enable 10.5 as a minimum target version
>> 
>> Modified Paths:
>> --
>>trunk/dports/security/certsync/Portfile
>> 
>> Modified: trunk/dports/security/certsync/Portfile
>> ===
>> --- trunk/dports/security/certsync/Portfile  2013-08-15 21:57:55 UTC (rev 
>> 109459)
>> +++ trunk/dports/security/certsync/Portfile  2013-08-15 22:01:38 UTC (rev 
>> 109460)
>> @@ -38,7 +38,7 @@
>> build {
>>  system -W ${worksrcpath} "${configure.objc} \
>>  ${configure.objcflags} \
>> --mmacosx-version-min=10.6 \
>> +-mmacosx-version-min=10.5 \
> 
> Shouldn't this be using $macosx_deployment_target?
> 
> And presumably this means that the code doesn't work on 10.4, so other
> ports shouldn't depend on certsync on 10.4?


do we care about 10.4 (I don't think we should). The only reason why it's a 
little bit reasonable to care about 10.5 is that it's the last release that 
runs on ppc machines.

In both cases, Apple isn't releasing updates for them anymore...
--
Daniel J. Luke  
 
++  
  
| * dl...@geeklair.net * |  

| *-- http://www.geeklair.net -* |  

++  
  
|   Opinions expressed are mine and do not necessarily   |  

|  reflect the opinions of my employer.  |  

++



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


[109460] trunk/dports/security/certsync/Portfile

2013-08-15 Thread Joshua Root
> Revision: 109460
>   https://trac.macports.org/changeset/109460
> Author:   landonf at macports.org
> Date: 2013-08-15 15:01:38 -0700 (Thu, 15 Aug 2013)
> Log Message:
> ---
> Enable 10.5 as a minimum target version
> 
> Modified Paths:
> --
> trunk/dports/security/certsync/Portfile
> 
> Modified: trunk/dports/security/certsync/Portfile
> ===
> --- trunk/dports/security/certsync/Portfile   2013-08-15 21:57:55 UTC (rev 
> 109459)
> +++ trunk/dports/security/certsync/Portfile   2013-08-15 22:01:38 UTC (rev 
> 109460)
> @@ -38,7 +38,7 @@
>  build {
>   system -W ${worksrcpath} "${configure.objc} \
>   ${configure.objcflags} \
> - -mmacosx-version-min=10.6 \
> + -mmacosx-version-min=10.5 \

Shouldn't this be using $macosx_deployment_target?

And presumably this means that the code doesn't work on 10.4, so other
ports shouldn't depend on certsync on 10.4?

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev