Changes between Version 118 and Version 119 of FAQ

Timestamp:

Dec 10, 2011, 8:08:24 AM (13 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

mention subports in dependonvariant section

FAQ

@@ -228 +228 @@
 === Is it possible to have a dependency on a specific variant of another port? E.g. "postgresql8 +server"? === #dependonvariant
 
-No.  This is ticket #126.  The dependency engine is currently unable to handle specifying anything beyond "port X requires port Y" or "port X requires file Z which can be provided by port Y."  There have been discussions on revamping the engine (see the mailing list archives) but nothing concrete as yet.  This is why the most useful variants really shouldn't be variants at all but rolled into the port itself.  It can also sometimes be useful to break variants out into separate ports (e.g. the postgresql83-doc and postgresql83-server ports, instead of having +doc or +server variants of the postgresql83 port).
+No.  This is ticket #126.  The dependency engine is currently unable to handle specifying anything beyond "port X requires port Y" or "port X requires file Z which can be provided by port Y."  There have been discussions on revamping the engine (see the mailing list archives) but nothing concrete as yet.  This is why the most useful variants really shouldn't be variants at all but rolled into the port itself.  It can also sometimes be useful to break variants out into subports or separate ports (e.g. the postgresql83-doc and postgresql83-server ports, instead of having +doc or +server variants of the postgresql83 port).
 
 === Why won't `portindex` work? I have a local repository set up === #portindexfails