Re: pypi

On Jun 22, 2015, at 4:18 PM, Mojca Miklavec wrote: > I have a tendency to delete > e-mails with subject that looks like a reply to a SVN commit and so > might others. I encourage you and others to read responses to commits. I often provide code reviews in such emails, and others do as well. Eve

Re: pypi

On Jun 22, 2015, at 5:01 PM, Lawrence Velázquez wrote: >> BTW: would be great if we could get rid of these constructs which appear in >> all ports. >> >> if {${subport} ne ${name}} { >> >> livecheck.type none >> } else { >> livecheck.type pypi >> } > > Yes, this would also go into the po

Re: Setting up MacPorts libsolv branch and Testing libsolv search

On 2015-6-23 01:11 , Clemens Lang wrote: > Hi, > > - On 22 Jun, 2015, at 15:04, Rainer Müller rai...@macports.org wrote: > >> Please excuse my ignorance here, but 'port search' merely queries the >> index for matching ports. Why do we need a SAT solver for this? What is >> the expected advant

Re: github portgroup design (was: Re: [MacPorts] #47951: tmux: moved from SF to Github)

I like this discussion on portgroup design very much, also because I was trying to come up with a Globus portgroup. I was quite puzzled on how it should work, and I actually started from the Github group. At the end I found myself experimenting with two version, one with setup procedure one wit

Re: pypi

On Jun 22, 2015, at 5:54 PM, petr <9...@ingv.it> wrote: > I personally -- and I guess this is in line with what Lawrence is proposing > -- would integrate this into the Python portgroup itself, where one could > have the following by default set. > > python.use_pypi yes > > This would set all

Re: pypi

Hi Lawrence, Hi Mojca, I also had this in mind for quite some while, however I got stuck on several issues, when testing. So I wanted to get these fixed as well, but never found the time. On 22 Jun 2015, at 23:12, Lawrence Velázquez wrote: > On Jun 22, 2015, at 4:59 PM, Mojca Miklavec wrote

Re: pypi

On Jun 22, 2015, at 5:42 PM, Sterling Smith wrote: > Just so I’m clear - are the portgroups part of macports base or part of the > port database? The latter. > Basically, if I do a `port selfupdate` do I get them, or only when there is a > new release of macports? The former. > I can see py

Re: github portgroup design (was: Re: [MacPorts] #47951: tmux: moved from SF to Github)

On Jun 4, 2015, at 7:32 PM, Ryan Schmidt wrote: > I agree setup procs are not the best. I also don't like that the semantics of the arguments are not obvious. We might know from experience what the different components of github.setup foo bar 1.0 foo- mean, but it doesn't lend itself to b

Re: pypi

Just so I’m clear - are the portgroups part of macports base or part of the port database? Basically, if I do a `port selfupdate` do I get them, or only when there is a new release of macports? I can see python.rootname (which looks like it cuts off the `py-` prefix) would be very useful in a

Re: pypi

On Jun 22, 2015, at 5:18 PM, Mojca Miklavec wrote: > OK, I agree. Something in the Python PortGroup could take care of > these settings, but in any case the defaults should not influence all > python ports. You would end up with > PortGroup python 1.0 > pypi_something something I'm not sure

Re: pypi

On Mon, Jun 22, 2015 at 11:12 PM, Lawrence Velázquez wrote: > On Jun 22, 2015, at 4:59 PM, Mojca Miklavec wrote: > >> Also: wouldn't it be nice to have some pypi portgroup that would >> automatically set: >> - livecheck >> - distname >> - homepage >> - master_sites >> and possibly other things. >>

Re: pypi

On Jun 22, 2015, at 4:59 PM, Mojca Miklavec wrote: > Also: wouldn't it be nice to have some pypi portgroup that would > automatically set: > - livecheck > - distname > - homepage > - master_sites > and possibly other things. > > The following expression: >master_sitespypi:[string ind

Re: pypi

On Jun 22, 2015, at 4:49 PM, Mojca Miklavec wrote: > On Mon, Jun 22, 2015 at 10:05 PM, Lawrence Velázquez wrote: > >> Please consider using the new "pypi" fetch group and livecheck type. For >> example: >> >> http://trac.macports.org/browser/trunk/dports/python/py-vcversioner/Portfile?rev=13788

python: finding specific library version via CMake

Hi, I have a CMake file that has the following, hopefully self-explanatory, bit: {{{ find_package(PythonLibs 3.4.3 REQUIRED) if ( NOT ${PYTHONLIBS_FOUND} OR ${PYTHON_VERSION_MINOR} GREATER 4 ) message(FATAL_ERROR "Python 3.4.3 with --enable-shared is required") endif() }}} The only thing tha

Re: pypi

On Mon, Jun 22, 2015 at 10:49 PM, Mojca Miklavec wrote: > On Mon, Jun 22, 2015 at 10:05 PM, Lawrence Velázquez wrote: >> Please consider using the new "pypi" fetch group and livecheck type. For >> example: >> >> http://trac.macports.org/browser/trunk/dports/python/py-vcversioner/Portfile?rev=137886

pypi

(was: [137886] users/mojca/ports/python) On Mon, Jun 22, 2015 at 10:05 PM, Lawrence Velázquez wrote: > Please consider using the new "pypi" fetch group and livecheck type. For > example: > > http://trac.macports.org/browser/trunk/dports/python/py-vcversioner/Portfile?rev=137886 This should also b

Re: [137886] users/mojca/ports/python

Please consider using the new "pypi" fetch group and livecheck type. For example: http://trac.macports.org/browser/trunk/dports/python/py-vcversioner/Portfile?rev=137886 Also, you should use Tcl's "file a

Re: embracing go compiler

On Mon, Jun 22, 2015 at 6:12 PM, Jeremy Lavergne wrote: > > Since there's has not been notable discussion on using Go compiler in > MacPorts, it would advantageous to start on a PortGroup while there's only > six portfiles to fixup. I have another one on my TODO list. If a PortGroup will be ava

Re: embracing go compiler

Certainly. While MacPorts has six Go-using portfiles, I'm seeing many more listed on just the first-google-hit: http://go-lang.cat-v.org/go-code Since there's has not been notable discussion on using Go compiler in MacPorts, it would advantageous to start on a PortGroup while there's only six po

Re: embracing go compiler

On Jun 22, 2015, at 11:32 AM, Jeremy Lavergne wrote: > Will MacPorts set the appropriate compiler flags for the Go compiler? I > suspect Go is popular enough to warrant some attention in base if someone has > time. Go might benefit from a portgroup, but I don't think it deserves special trea

embracing go compiler

Will MacPorts set the appropriate compiler flags for the Go compiler? I suspect Go is popular enough to warrant some attention in base if someone has time. For example, see the MP_GOFLAGS in build.args for: https://trac.macports.org/browser/trunk/dports/sysutils/asciinema/Portfile __

Re: Setting up MacPorts libsolv branch and Testing libsolv search

- On 22 Jun, 2015, at 16:34, Ryan Schmidt ryandes...@macports.org wrote: > It would be good if libsolv would be installed automatically when this branch > is > installed (much like Tcl is automatically installed). The absence of this > functionality means that building the branch will fail

Re: Setting up MacPorts libsolv branch and Testing libsolv search

Hi, - On 22 Jun, 2015, at 15:04, Rainer Müller rai...@macports.org wrote: > Please excuse my ignorance here, but 'port search' merely queries the > index for matching ports. Why do we need a SAT solver for this? What is > the expected advantage? Searching is just a dummy use case we can use

Re: Setting up MacPorts libsolv branch and Testing libsolv search

Hi Ryan, On Mon, Jun 22, 2015 at 8:04 PM, Ryan Schmidt wrote: > > Thanks. I read the post but haven't tried installing the branch yet. > > It would be good if libsolv would be installed automatically when this branch > is installed (much like Tcl is automatically installed). The absence of this

Re: Setting up MacPorts libsolv branch and Testing libsolv search

On Jun 20, 2015, at 7:28 AM, Jackson Isaac wrote: > I have been working on implementing libsolv SAT Solver in MacPorts as > part of GSoC 2015 with my mentor, Clemens Lang. > > Currently we have implemented search using libsolv and added an option > -l to use libsolv for the same. > > I would li

Re: Setting up MacPorts libsolv branch and Testing libsolv search

Hi Rainer, On Mon, Jun 22, 2015 at 6:34 PM, Rainer Müller wrote: > > thank you for the report. It's good to see you are making progress as > midterm is already approaching. > Thanks :) > On 2015-06-20 14:28, Jackson Isaac wrote: >> Currently most of the options that are available in builtin sea

Re: Setting up MacPorts libsolv branch and Testing libsolv search

Hey Jackson, thank you for the report. It's good to see you are making progress as midterm is already approaching. On 2015-06-20 14:28, Jackson Isaac wrote: > Currently most of the options that are available in builtin search > "port help search" have also been made available with libsolv. More >