[MacPorts] #26568: Updated yap portfile
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap-devel ---------------------------------+------------------------------------------ Added some of the most used variants to the portfile. Changes the default variants as the threads one is currently broken. -- Ticket URL: <https://trac.macports.org/ticket/26568> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap-devel ---------------------------------+------------------------------------------ Comment(by pmoura@…): Oops! the port field is wrongly set to "yap-devel" instead of "yap"! But I have no permission to correct it. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * port: yap-devel => yap Comment: {{{ $ port lint yap ---> Verifying Portfile for yap Warning: Variant tabling does not have a description Warning: Variant threads does not have a description Error: Variant name depth-limit is not valid; use [A-Za-z0-9_]+ only Warning: Variant cplint does not have a description Warning: Variant coroutining does not have a description ---> 1 errors and 4 warnings found. }}} Also, fewer variants would be better... Can any of these variants be removed and just be always on or always off? Does the user really want control over all these options? -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Comment(by pmoura@…): I'm afraid this is just an initial set of variants that don't cover all the the possible configuration options. YAP is widely used in the area of Logic Programming research and supports a large set of optional packages. I only defined variants for the most commonly used optional packages. I didn't add descriptions to the variants are their name is quite descriptive for YAP users. I will correct the error with the variant name after this reply. I'm going to contact the YAP main developer and ask him about which variants are useful to define. Please hold the commit of this portfile and of the "yap-devel" portfile for a couple of days until I sort this out. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Comment(by pmoura@…): Talked with the YAP developer today and updated the portfile patch accordingly. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Comment(by ryandesign@…): I am not a YAP user so you will have to bear with me. :) None of these variants add dependencies, so they appear to just be adding internal YAP features. Is there any disadvantage to enabling them all the time, or any advantage to disabling them? For example, you have defined a variant "tabling" which is in the default_variants. Is there any reason why a user would ever want to disable this? And you have defined the variant "condor" but it's not on by default. Why would a user not want this? Just trying to understand why YAP is different from other software, where we prefer to always compile in all possible options (unless they bring in big dependencies, in which case we might make variants). -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Comment(by pmoura@…): Some of the features are not stable or hurt performance or are incompatible with dynamic loading. So, you only enable them if you absolutely need it. I'm chatting with the YAP developer on Skype about it. He prefers that tabling is not a default so I'm going to submit updated portfiles for yap and yap-devel next. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Comment(by pmoura@…): Just upload a new patch file that removes tabling from the default variants as, accordingly to the YAP developer, is not stable enough to be a default. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: ryandesign@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * status: new => assigned * owner: macports-tickets@… => ryandesign@… Comment: Ok, we'll add the variants. I tried to build it with this patch and the first thing the configure script says is {{{ configure: WARNING: unrecognized options: --with-java }}} It builds, but if that configure argument is unrecognized, I wonder if the +java variant is actually doing anything. Looking at the output of "./configure --help" I see: {{{ --with-jpl=JAVA_HOME use Java instalation in JAVA_HOME }}} Is that the option you meant? We'll also want to increase the port's revision since this patch changes the contents of the installed files. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: ryandesign@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Comment(by pmoura@…): Your message above about the Java option confused me a bit. It turns out that the option is named "--with-jpl" on YAP 6.05 but renamed to "--with- java" in 6.0.6 stable (which give a build error when using MacPorts) and 6.0.7 (the current development version, which fixes the build issue in 6.0.6). Thus, for the "yap" port, we need "--with-jpl". Can you make the change or do you prefer that I submit a corrected patch? Sorry for the trouble. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: ryandesign@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch maintainer | Port: yap ---------------------------------+------------------------------------------ Comment(by ryandesign@…): It's fine; you don't need to attach another patch. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26568: Updated yap portfile ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: ryandesign@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Resolution: fixed | Keywords: haspatch maintainer Port: yap | ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * status: assigned => closed * resolution: => fixed Comment: Updated yap in r71889, using mostly your patch with a few changes. -- Ticket URL: <https://trac.macports.org/ticket/26568#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts