is archcheck portgroup history?
Ryan Schmidt
ryandesign at macports.org
Fri Aug 6 14:40:59 PDT 2010
On Aug 6, 2010, at 16:23, Bradley Giesbrecht wrote:
> On Aug 6, 2010, at 2:00 PM, Ryan Schmidt wrote:
>
>> On Aug 6, 2010, at 15:47, Bradley Giesbrecht wrote:
>>
>>>>> Could we use lipo on it and append the registry rather then rebuild?
>>>>
>>>> How would MacPorts know which file to lipo? Should it try all of them until it finds one that is a binary and use that? What if the port installs files that aren't all the same architecture?
>>>
>>> How does it use lipo now?
>>
>> Currently, ports using the archcheck portgroup must specify which file to lipo.
>
> I am creating a dovecot2 port for the upcoming release of dovecot v2 and archcheck was in the dovecot v1 port.
>
> I was wanting to understand what archcheck does and if it was still needed.
>
> Should I add portgroup archcheck to the new dovecot2 port?
Doing so might save your users some aggravation and save you some bug reports. If MacPorts' built-in architecture checking improves in the future you can always remove the archcheck portgroup from the port later.
More information about the macports-dev
mailing list