<html><head><style>body{font-family:Merriweather,Arial;font-size:13px}</style></head><body><div style="font-family:Merriweather,Arial;font-size:13px;color:rgba(51,51,51,1.0)">I mean, you can maybe describe the “feature set” of the prebuilt binary in the variant description and forbid all the other variants… Can’t you? </div><div style="font-family:Merriweather,Arial;font-size:13px;color:rgba(51,51,51,1.0)"><br></div><div style="font-family:Merriweather,Arial;font-size:13px;color:rgba(51,51,51,1.0)">PS: Maybe “prebuilt_binary” is not the right wording since most of the ports can already be installed as “prebuilt_binary”. Maybe it should be something like “bin_only” ?</div><div style="font-family:Merriweather,Arial;font-size:13px;color:rgba(51,51,51,1.0)"><br></div><div style="font-family:Merriweather,Arial;font-size:13px;color:rgba(51,51,51,1.0)">PPS: As I already said, ports that are open source should be fixed at least on the buildbot machines in order to be able to build them from sources (as the upstream developer did) allowing few, highly selected, exceptions (as the java stuff that was already mentioned). </div> <div class="gmail_signature"><pre><code> _
-. .´ |∞∞∞∞
', ; |∞∞∞∞∞∞
˜˜ |∞∞∞∞∞∞∞∞∞ RdB
,., |∞∞∞∞∞∞
.' '. |∞∞∞∞
-' `’
<a href="https://rdb.is">https://rdb.is</a>
</code></pre></div> <br><p class="airmail_on">On 15 August 2020 at 01:11:23, Ken Cunningham (<a href="mailto:ken.cunningham.webuse@gmail.com">ken.cunningham.webuse@gmail.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>consider:
<br>
<br>$ port variants macvim
<br>Warning: port definitions are more than two weeks old, consider updating
<br>them by running 'port selfupdate'.
<br>MacVim has the variants:
<br> big: Build big feature set
<br> * conflicts with huge
<br> cscope: Enable source code browsing with cscope
<br>[+]huge: Build huge feature set
<br> * conflicts with big
<br> lua: Enable Lua scripting
<br> perl: Enable Perl scripting
<br> python27: Enable Python scripting
<br> python36: Enable Python scripting
<br> * conflicts with python37
<br> python37: Enable Python scripting
<br> * conflicts with python36
<br> ruby: Compatibility variant, requires +ruby18
<br> * requires ruby18
<br> ruby18: Enable Ruby scripting
<br> * conflicts with ruby19 ruby20 ruby21 ruby22 ruby23 ruby24 ruby25
<br> ruby19: Enable Ruby scripting
<br> * conflicts with ruby18 ruby20 ruby21 ruby22 ruby23 ruby24 ruby25
<br> ruby20: Enable Ruby scripting
<br> * conflicts with ruby18 ruby19 ruby21 ruby22 ruby23 ruby24 ruby25
<br> ruby21: Enable Ruby scripting
<br> * conflicts with ruby18 ruby19 ruby20 ruby22 ruby23 ruby24 ruby25
<br> ruby22: Enable Ruby scripting
<br> * conflicts with ruby18 ruby19 ruby20 ruby21 ruby23 ruby24 ruby25
<br> ruby23: Enable Ruby scripting
<br> * conflicts with ruby18 ruby19 ruby20 ruby21 ruby22 ruby24 ruby25
<br> ruby24: Enable Ruby scripting
<br> * conflicts with ruby18 ruby19 ruby20 ruby21 ruby22 ruby23 ruby25
<br> ruby25: Enable Ruby scripting
<br> * conflicts with ruby18 ruby19 ruby20 ruby21 ruby22 ruby23 ruby24
<br> tcl: Enable Tcl scripting
<br> xim: Build with support for X Input Method
<br>
<br>
<br>
<br>so -- what would a user typing
<br>
<br>sudo port -v install macvim +prebuild_binary -huge +big +ruby25 +tcl +xim
<br>
<br>be expected to get? It's a total shambles. Variants for this are not
<br>workable. So let's move on to a plan that might actually work. Or not.
<br>I think, as has been stated, that the whole idea is possibly too flawed
<br>to be considered.
<br>
<br>
<br>K
<br>
<br></div></div></span></blockquote></body></html>