On 08/31 01:22, Jeremy Evans wrote: > Another possible way to handle this would be to keep ruby 1.9 ports > using the ruby19 FLAVOR, but switch ruby 1.8 ports to use a ruby18 > FLAVOR, and have unFLAVORed builds just default to the ruby19 > FLAVOR. I'll consider that approach if the @conflict markers can be > added to the PLIST automatically by ruby.port.mk for ruby18 ports.
s/@conflict/@pkgpath/
