On Fri, 15 Jul 2005, Aleksander Piotrowski wrote:
What dependency tracker are you talking about?
Just the normal ports dependency mechanisms --- building another package before building this one, and putting accurate @foo lines in the final
package spec.
Maybe PSEUDO_FLAVOR and SUBPACKAGE can be used to do that? What does this gconf-sanity-check do anyway?
You're right, a pseudo-flavor and subpackage would be a better way to handle this. (I'm not 100% sure what the sanity-check program does, really; all I know is it's an optional troubleshooting tool for gconf's configuration database. I'm not the port's maintainer; I just want it to build cleanly so I can build some other things.)
