Arch checking

Ryan Schmidt ryandesign at macports.org
Sat Jun 12 06:34:00 PDT 2010


Now that MacPorts 1.9.0 records the architecture of each installed port in the registry, it would be nice if it would check that the port actually did install files of the architecture it claimed to, and when it doesn't, a warning would be printed. This would enable us to more easily notice which ports need a supported_archs line added. For example:


Prior to r68725:

$ sudo port install graphviz-oldgui
--->  Computing dependencies for graphviz-oldgui
--->  Fetching graphviz-oldgui
--->  Verifying checksum(s) for graphviz-oldgui
--->  Extracting graphviz-oldgui
--->  Applying patches to graphviz-oldgui
--->  Configuring graphviz-oldgui
--->  Building graphviz-oldgui
--->  Staging graphviz-oldgui into destroot
Warning: graphviz-oldgui claims to be installing for the arch(s) x86_64 but only installed files of the arch(s) ppc
Warning: See http://trac.macports.org/wiki/ArchCheck
--->  Installing graphviz-oldgui @16_0
--->  Activating graphviz-oldgui @16_0
--->  Cleaning graphviz-oldgui


Prior to r68751:

$ sudo port install gnome-icon-theme
--->  Computing dependencies for gnome-icon-theme
--->  Fetching gnome-icon-theme
--->  Verifying checksum(s) for gnome-icon-theme
--->  Extracting gnome-icon-theme
--->  Configuring gnome-icon-theme
--->  Building gnome-icon-theme
--->  Staging gnome-icon-theme into destroot
Warning: gnome-icon-theme claims to be installing for the arch(s) x86_64 but installed no architecture-specific files
Warning: See http://trac.macports.org/wiki/ArchCheck
--->  Installing gnome-icon-theme @2.26.0_0--->  Activating gnome-icon-theme @2.26.0_0
--->  Cleaning gnome-icon-theme


On the referenced wiki page we would describe what should be done in each case. (This goes back to a much earlier suggestion months or years ago that each error message should just be relatively short but should link to a wiki page where it can be explained in more detail in separate sections written to target users and port maintainers; we currently have the problem that some of our errors target users, some target maintainers, and some are too wordy.)




More information about the macports-dev mailing list