[73103] djview Lint Report

[Ryan Schmidt]

On Nov 3, 2010, at 21:17, Michael Dickens wrote:

>> Date: November 3, 2010 9:28:11 PM EDT
>> Subject: [73103] djview Lint Report
>> 
>> Change: http://trac.macports.org/changeset/73103
>> Portfile: djview
>> 
>> Can't map the URL 'file://.' to a port description file ("invalid command name "archcheck.files"").
>> Please verify that the directory and portfile syntax are correct.
>> To use the current port, you must be in a port's directory.
> 
> What does this mean?  I get it no matter if I use "archcheck.files" or "archcheck.files-append".  "port lint djview" comes back clean.  Should I just ignore this?  The ports that have reported back this issue do work (for me). - MLD

Due to this revision, the djview port does not work; attempting to use it produces the message quoted above.

If you want to use "archcheck.files" you need to include the archcheck 1.0 portgroup.

I wrote the archcheck portgroup some time ago to ensure dependencies of a port were installed with the right architecture, both to help people trying to rebuild a port universal or with a different build_arch (and forgetting or not knowing that they have to rebuild dependencies that way first) and to help users upgrading to Snow Leopard (some of whom whom did not know they needed to uninstall and reinstall all ports on Snow Leopard).

As of MacPorts 1.9.0, both of these situations are now handled by MacPorts base itself -- if you install a port universal, it will rebuild dependencies universal for you, and MacPorts now records the architecture with which the port claims to build in the registry -- so the archcheck portgroup isn't really needed anymore, for ports whose dependencies have been upgraded after MacPorts 1.9.0 was released and where those dependencies properly respect universal_archs and build_arch.

In this revision, you added archcheck for libQtCore.dylib (provided by qt4-mac) and libdjvulibre.dylib (provided by djvulibre), both of which were updated recently, well after the release of MacPorts 1.9.0, so unless qt4-mac or djvulibre do not respect universal_archs or build_arch, this manual archcheck is not needed.