On Jun 4, 2009, at 5:58 PM, Ryan Schmidt wrote:
On Jun 4, 2009, at 19:56, Ryan Schmidt wrote:
On Jun 4, 2009, at 19:52, Scott Haneda wrote:
port install assp
Within that port, assp will depend on clamav, but since I can not
define a variant for clamav +server, I have to make a clamav-
server port. Fine up to that point.
Now, what is I want clamav +server +clamav_milter available to the
assp port?
My port install command would be port install assp still, there
would still be a call in there to clamav-server, where does the
milter go in?
It does not.
When I spoke earlier about creating a clamav-server port, I was
speaking of the +server variant only, not any of the other
variants. The clamav_milter variant, for example, is, I believe,
integrated into the clamav software. The variant adds the configure
argument --enable-milter. This presumably causes the clamav
software to build additional libraries, or modify the libraries it
builds in some way. You probably can't separate that into a
separate port.
If there is a file clamav+clamav_milter installs that regular
clamav does not, you can detect the absence of that file in your
assp port and issue the appropriate error message. See the pango
port for an example (it checks that the cairo port is installed
with the correct variants).
Now that I actually come to look at the clamav portfile.... it
doesn't have a +server variant! So.... what are we talking about here?
We are talking about adding one. We have +server in our local repo.
When we have things the way we want we intend to write up some
documentation on setting up various services using MacPorts.
//Brad
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
