Forcing a variant to a variant

[Scott Haneda]

On Jun 4, 2009, at 4:18 PM, Ryan Schmidt wrote:

>> I think I understand why, and I think I understand the long term  
>> goal here, but the above has me wondering a little.
>>
>> Is it a terrible idea to pop in a second startup item in which will  
>> just instal the clamav startup item?  This seems messy to me, but  
>> it also will get the job done.
>
>
> The goal is not duplication, but separation, so that you can declare  
> dependencies on those separate parts. The clamav port would then  
> install everything clamav except the server component, and the  
> clamav-server port would install only the clamav server component  
> (and depend on the clamav port). See the postgresql83 and  
> postgresql83-server ports, and the mysql5 and mysql5-server ports  
> (now committed), for examples.


Got it, thanks!  Not clear on postgresql83-server, that is a pretty  
large port to only install a start up item.  Why isnt all that work  
happening in the postgresql83 port?

Off list I was given this:

`port echo variants:server`

boxbackup
cacti
makuosan
monarch
munin
mysql3
mysql4
mysql5
mysql5-devel
nedi
net-snmp
netmrg
nrg
nsd
perforce
postgresql7
sendpage
sleepwatcher
snort
subversion
sympa
synergy
tftp-hpa
tightvnc
vm-pop3d
vnc
xserve-raid-tools
zabbix

A few of those are done already.  Is closing #126 just a matter of  
splitting the above ports into two, and having on depend on the other  
with a startup item in it?  That ticket is 7 years old, if the list  
above is all it takes to close it, maybe I can find a weekend
-- 
Scott * If you contact me off list replace talklists@ with scott@ *