port "cask" -- installing prebuilt binaries

[Ruben Di Battista]

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?

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” ?

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).

          _
-.     .´  |∞∞∞∞
  ',  ;    |∞∞∞∞∞∞
    ˜˜     |∞∞∞∞∞∞∞∞∞ RdB
    ,.,    |∞∞∞∞∞∞
  .'   '.  |∞∞∞∞
-'       `’
https://rdb.is


On 15 August 2020 at 01:11:23, Ken Cunningham (
ken.cunningham.webuse at gmail.com) wrote:

consider:

$ port variants macvim
Warning: port definitions are more than two weeks old, consider updating
them by running 'port selfupdate'.
MacVim has the variants:
   big: Build big feature set
     * conflicts with huge
   cscope: Enable source code browsing with cscope
[+]huge: Build huge feature set
     * conflicts with big
   lua: Enable Lua scripting
   perl: Enable Perl scripting
   python27: Enable Python scripting
   python36: Enable Python scripting
     * conflicts with python37
   python37: Enable Python scripting
     * conflicts with python36
   ruby: Compatibility variant, requires +ruby18
     * requires ruby18
   ruby18: Enable Ruby scripting
     * conflicts with ruby19 ruby20 ruby21 ruby22 ruby23 ruby24 ruby25
   ruby19: Enable Ruby scripting
     * conflicts with ruby18 ruby20 ruby21 ruby22 ruby23 ruby24 ruby25
   ruby20: Enable Ruby scripting
     * conflicts with ruby18 ruby19 ruby21 ruby22 ruby23 ruby24 ruby25
   ruby21: Enable Ruby scripting
     * conflicts with ruby18 ruby19 ruby20 ruby22 ruby23 ruby24 ruby25
   ruby22: Enable Ruby scripting
     * conflicts with ruby18 ruby19 ruby20 ruby21 ruby23 ruby24 ruby25
   ruby23: Enable Ruby scripting
     * conflicts with ruby18 ruby19 ruby20 ruby21 ruby22 ruby24 ruby25
   ruby24: Enable Ruby scripting
     * conflicts with ruby18 ruby19 ruby20 ruby21 ruby22 ruby23 ruby25
   ruby25: Enable Ruby scripting
     * conflicts with ruby18 ruby19 ruby20 ruby21 ruby22 ruby23 ruby24
   tcl: Enable Tcl scripting
   xim: Build with support for X Input Method



so -- what would a user typing

sudo port -v install macvim +prebuild_binary -huge +big +ruby25 +tcl +xim

be expected to get? It's a total shambles. Variants for this are not
workable.  So let's move on to a plan that might actually work. Or not.
I think, as has been stated, that the whole idea is possibly too flawed
to be considered.


K
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20200814/1f4e0a1f/attachment-0001.htm>