Re: [113549] trunk/www/install.php

2013-11-20 Thread Lawrence Velázquez 
On Nov 20, 2013, at 9:13 AM, Joshua Root  wrote:

> On 2013-11-20 12:37 , Ryan Schmidt wrote:
>> 
>> On Nov 19, 2013, at 19:33, Jeremy Lavergne wrote:
>> 
>>> Really? Twice on the license?
>> 
>> Yes, as we already documented previously, right? This is not new for 
>> Mavericks.
> 
> I'm pretty sure you don't have to accept the license both system-wide
> and for the current user. Just system-wide should suffice. Just for the
> current user obviously won't.

I've only ever accepted system-wide, without issue.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [113456] trunk/dports/textproc

2013-11-20 Thread Ryan Schmidt 

On Nov 16, 2013, at 08:07, h...@macports.org wrote:

> Revision
> 113456
> Author
> h...@macports.org
> Date
> 2013-11-16 06:07:30 -0800 (Sat, 16 Nov 2013)
> Log Message
> 
> New port: brown-cluster @ 1.3-20130905 - C++ implementation of the Brown word 
> clustering algorithm.
> Added Paths
> 
>   • trunk/dports/textproc/brown-cluster/
>   • trunk/dports/textproc/brown-cluster/Portfile
>   • trunk/dports/textproc/brown-cluster/files/
>   • trunk/dports/textproc/brown-cluster/files/patch-Makefile.diff
>   • trunk/dports/textproc/brown-cluster/files/patch-cpp11.diff
> Diff
> 
> Added: trunk/dports/textproc/brown-cluster/Portfile (0 => 113456)
> 
> --- trunk/dports/textproc/brown-cluster/Portfile  
> (rev 0)
> +++ trunk/dports/textproc/brown-cluster/Portfile  2013-11-16 14:07:30 UTC 
> (rev 113456)
> 
> @@ -0,0 +1,39 @@
> 
> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; 
> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
> +# $Id$
> +
> +PortSystem  1.0
> +PortGroup   github 1.0
> +
> +github.setuppercyliang brown-cluster 
> add013e2d42e69b3dda505b2d54fe3f52650a4df
> +
> +version 1.3-20130905
> +categories  textproc
> +maintainers hum openmaintainer
> +
> +description C++ implementation of the Brown word clustering algorithm
> +long_description${description}.
> +
> +platforms   darwin
> +license Permissive
> +
> +checksums   rmd160  daaf19aac15030689c771c09bdc0b1a9c2db452b \
> +sha256  
> 249bcc66277f1d72c81ece3bf0d28af66ec3cfbae8e6fb16bf3d7caff82a2401
> +
> +patchfiles  patch-Makefile.diff patch-cpp11.diff
> +
> +use_configure   no
> +
> +build.targetwcluster
> +build.args  CXX="${configure.cxx}" \
> +CXXFLAGS="${configure.cxxflags} [get_canonical_archflags 
> cxx]"

Is there any reason why we shouldn’t add a universal variant? It seems to build 
fine for me.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

commit request: #41334 py-pyshp@1.2.0 / #41337 py-cartopy @0.9.0

2013-11-20 Thread Peter Danecek 

Hi committers,

could someone have look at two of my submissions, they are related (one is a 
dependency of the other). 

https://trac.macports.org/ticket/41334
https://trac.macports.org/ticket/41337

I case you have some doubt with these, please comment.

~petr



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Vote: mysql5 replaced_by ?

2013-11-20 Thread Craig Treleaven 

At 11:02 AM -0800 11/20/13, Bradley Giesbrecht wrote:

On Nov 19, 2013, at 4:58 PM, Ryan Schmidt wrote:



 On Nov 19, 2013, at 15:15, Joshua Root wrote:

 On 2013-11-20 07:45 , Bradley Giesbrecht wrote:

 Popular choices:
 mysql55
 mysql56
 mariadb
 mariadb55 (mariadb replaced_by mariadb55)


 My vote:
 +1 mariadb55


 mysql5 is 5.1, so really the only option is to replace it with mysql51.


 Agreed because the whole reason why we have separate ports for 
different versions of database servers is so that users can do it 
at a time of their choosing, since doing so may necessitate 
upgrading the database structure and/or changing the user's code 
which uses the database.


Ok, just to be clear, replacing mysql5 with mysql51 will likely 
require users to move there database files and config files.


I was going to stay out of this, but...

If mysql5 is going away and work has to be done to affect the change, 
it makes no sense to me to _not_ go with a 5.5 or even 5.6 version 
(be that MySQL or Maria).


Could we not find a way to have a 'mysql-current*'?  There have got 
to be a number of ports that currently depend on MySQL but have no 
fundamental problem with newer versions.  (My mythtv-core.xx ports 
fall in that group.)  The mysql-current port would just provide a way 
of finding the version-specific binaries and libraries. 
mysql-current might point to mysql55 right now and later be updated 
to maria56, or whatever, while being as transparent as possible.


I think the current situation with mysql-compatible databases is a 
support nightmare.  For my ports, I want/need to give users 
cookbook-style instructions for installing Myth.  They have to do 6 
steps to install, initialize, load and prep the database.  If I were 
to support mysql, maria and percona, those instructions would be 
oh-so-subtly-different for each variant.  Already, I get quite a few 
questions where folks mucked up or missed a step.  I don't want to 
compound those issues several-fold!


Craig

*Yes, bad name.  Could be 'mysql-stable', 'mysql-blessed', 
'mysql-with-a-bullet', ...  ;)

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

using `numpy.distutils` / f2py ...

2013-11-20 Thread Peter Danecek 

Hi all, 

I have some problems with using `f2py` when building a package with Macports, 
while the same packages builds out of the box when when using `pip` in a 
`virtualenv`. I understand now what the problem is with that (no real solution 
yet), and I might be inclined to argue, that f2py should know how to correctly 
build out of the box. 

So I am wondering which other port is using numpy.distutils / numpy.f2py to 
build, if any. So that I can inspect that port first.

Thanks!
~petr




smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Vote: mysql5 replaced_by ?

2013-11-20 Thread Bradley Giesbrecht 

On Nov 19, 2013, at 4:58 PM, Ryan Schmidt wrote:

> 
> On Nov 19, 2013, at 15:15, Joshua Root wrote:
>> On 2013-11-20 07:45 , Bradley Giesbrecht wrote:
>>> Popular choices:
>>> mysql55
>>> mysql56
>>> mariadb
>>> mariadb55 (mariadb replaced_by mariadb55)
>>> 
>>> 
>>> My vote:
>>> +1 mariadb55
>> 
>> mysql5 is 5.1, so really the only option is to replace it with mysql51.
> 
> Agreed because the whole reason why we have separate ports for different 
> versions of database servers is so that users can do it at a time of their 
> choosing, since doing so may necessitate upgrading the database structure 
> and/or changing the user’s code which uses the database.


Ok, just to be clear, replacing mysql5 with mysql51 will likely require users 
to move there database files and config files.


Regards,
Bradley Giesbrecht (pixilla)

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

port select python ...

2013-11-20 Thread Peter Danecek 

Hi all,

this may be a very subtile detail and should never surface for Macports itself, 
but as I came across while hunting, I just ask. I am wondering if 

port select python

should not set a symlink, as follows as well:

libpython.dylib -> libpython2.7.dylib

The system has an analog symlink, and maybe this could become relevant while 
building some packages manually, in some cases? 

Just for consistency!
Just asking …
~petr



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [113549] trunk/www/install.php

2013-11-20 Thread Jeremy Lavergne 
Confirmed: installing xcode through the dialog does not also install the  
CLT. You need to run it twice: once for xcode (or manually go to the  
store) and once for CLT.


On Wed, 20 Nov 2013 03:18:24 -0500, Rainer Müller   
wrote:



On 2013-11-20 03:19, Ryan Schmidt wrote:
Presently inferring that the store page didn't do the command line  
tools for you. Will the dialog do so?


I don’t know. The wording of the dialog makes it sound like it will  
install both Xcode and the command line tools.

Installing Xcode only will make tools like /usr/bin/clang work, as they
are shims that either ask you to install Xcode/CLT or, if Xcode is
already installed, they use the tools provided in  
/Applications/Xcode.app.

However, if you do not install the CLT explicitly, you will miss some
files such as the infamous tclConfig.sh that is required to build
MacPorts itself.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [113549] trunk/www/install.php

2013-11-20 Thread Joshua Root 
On 2013-11-20 12:37 , Ryan Schmidt wrote:
> 
> On Nov 19, 2013, at 19:33, Jeremy Lavergne wrote:
> 
>> Really? Twice on the license?
> 
> Yes, as we already documented previously, right? This is not new for 
> Mavericks.

I'm pretty sure you don't have to accept the license both system-wide
and for the current user. Just system-wide should suffice. Just for the
current user obviously won't.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] howto/SyncingWithSVN modified

2013-11-20 Thread Joshua Root 
On 2013-11-20 20:58 , Rainer Müller wrote:
> On 2013-11-20 04:19, MacPorts wrote:
>> Page "howto/SyncingWithSVN" was changed by co...@ccs.neu.edu
>> Diff URL: 
>> 
>> Revision 12
>> Comment: Added SVN proxy and certificate configuration instructions.
>> Changes:
>> ---8<--8<--8<--8<--8<--8<--8<--8<
>> Index: howto/SyncingWithSVN
>> =
>> --- howto/SyncingWithSVN (version: 11)
>> +++ howto/SyncingWithSVN (version: 12)
>> @@ -44,11 +44,22 @@
>>  file://$prefix/var/macports/sources/svn.macports.org/trunk/dports/ [default]
>>  }}}
>>  
>> +=== Step 3: '''Configure Subversion''' ===
>>  
>> +First, tell subversion to use your proxy to connect to the server:
>> +1. If $prefix/var/macports/home/.subversion/servers doesn't exist, create 
>> it by copying the corresponding file from another user.  (SVN automatically 
>> creates this file if it doesn't exist.)
>> +2. Edit the file and set a proxy for hosts at `*.macports.org`.  Different 
>> proxy configurations require different sets of options here, but the file is 
>> pretty well commented, so it should be easy to figure out what you need.  At 
>> a minimum you'll need settings for http-proxy-host and http-proxy-port.
>> +
>> +Finally, if you want to use SVN over HTTPS to access the repository, you'll 
>> need to tell SVN to trust the MacPorts signature.  (SVN doesn't trust the 
>> authority that issued it, and `port sync` below invokes `svn up` with the 
>> `--non-interactive` flag, so you won't have the opportunity to accept the 
>> certificate then.)
>> +1. `mkdir -p $prefix/var/macports/home/.subversion/auth/svn.ssl.server`
>> +2. As a normal user, run `svn ls 
>> https://svn.macports.org/repository/macports/trunk/dports/`.  When prompted, 
>> accept the certificate permanently.
>> +3. SVN will store the certificate in a file in the directory 
>> `$HOME/.subversion/auth/svn.ssl.server`.  In that directory, find the file 
>> that contains the string "`https://svn.macports.org`"; and copy it into 
>> `$prefix/var/macports/home/.subversion/auth/svn.ssl.server`.
>> +
>> +Or, you can use SVN over HTTP, in which case you don't need to worry about 
>> the certificate.
> 
> Wouldn't this only be a problem if the Subversion checkout is owned by
> the macports user? If it's owned by your user account it should also use
> the same configuration files.

Also, the certificate trust is only a problem on certain versions of OS
X, and it's not just the certs for macports.org, the system svn doesn't
trust (or know about) any root certificates.

This can be worked around by doing the initial checkout manually and
then installing the subversion port. And of course forcing svn to trust
the cert that first time is potentially insecure, so you really ought to
verify the fingerprint it shows in any case. (And using http instead of
https just ensures the insecurity.)

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] howto/SyncingWithSVN modified

2013-11-20 Thread Rainer Müller 
On 2013-11-20 04:19, MacPorts wrote:
> Page "howto/SyncingWithSVN" was changed by co...@ccs.neu.edu
> Diff URL: 
> 
> Revision 12
> Comment: Added SVN proxy and certificate configuration instructions.
> Changes:
> ---8<--8<--8<--8<--8<--8<--8<--8<
> Index: howto/SyncingWithSVN
> =
> --- howto/SyncingWithSVN (version: 11)
> +++ howto/SyncingWithSVN (version: 12)
> @@ -44,11 +44,22 @@
>  file://$prefix/var/macports/sources/svn.macports.org/trunk/dports/ [default]
>  }}}
>  
> +=== Step 3: '''Configure Subversion''' ===
>  
> +First, tell subversion to use your proxy to connect to the server:
> +1. If $prefix/var/macports/home/.subversion/servers doesn't exist, create it 
> by copying the corresponding file from another user.  (SVN automatically 
> creates this file if it doesn't exist.)
> +2. Edit the file and set a proxy for hosts at `*.macports.org`.  Different 
> proxy configurations require different sets of options here, but the file is 
> pretty well commented, so it should be easy to figure out what you need.  At 
> a minimum you'll need settings for http-proxy-host and http-proxy-port.
> +
> +Finally, if you want to use SVN over HTTPS to access the repository, you'll 
> need to tell SVN to trust the MacPorts signature.  (SVN doesn't trust the 
> authority that issued it, and `port sync` below invokes `svn up` with the 
> `--non-interactive` flag, so you won't have the opportunity to accept the 
> certificate then.)
> +1. `mkdir -p $prefix/var/macports/home/.subversion/auth/svn.ssl.server`
> +2. As a normal user, run `svn ls 
> https://svn.macports.org/repository/macports/trunk/dports/`.  When prompted, 
> accept the certificate permanently.
> +3. SVN will store the certificate in a file in the directory 
> `$HOME/.subversion/auth/svn.ssl.server`.  In that directory, find the file 
> that contains the string "`https://svn.macports.org`"; and copy it into 
> `$prefix/var/macports/home/.subversion/auth/svn.ssl.server`.
> +
> +Or, you can use SVN over HTTP, in which case you don't need to worry about 
> the certificate.

Wouldn't this only be a problem if the Subversion checkout is owned by
the macports user? If it's owned by your user account it should also use
the same configuration files.

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: ticket #41122: py-obspy / maintainer haspatch

2013-11-20 Thread Peter Danecek 

Maybe I should have made clearer, that I am the maintainer and a patch is 
provided.
~petr


On Nov 19, 2013, at 21:03 , Peter Danecek  wrote:

> 
> Hi committers,
> 
> Can someone review the updated fix I just submitted to the ticket:
> 
>   https://trac.macports.org/ticket/41122
> 
> I am quite confident it should be all okay.
> 
> Thanks!
> ~petr
> 
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [113549] trunk/www/install.php

2013-11-20 Thread Rainer Müller 
On 2013-11-20 03:19, Ryan Schmidt wrote:
>> Presently inferring that the store page didn't do the command line tools for 
>> you. Will the dialog do so?
> 
> I don’t know. The wording of the dialog makes it sound like it will install 
> both Xcode and the command line tools.

Installing Xcode only will make tools like /usr/bin/clang work, as they
are shims that either ask you to install Xcode/CLT or, if Xcode is
already installed, they use the tools provided in /Applications/Xcode.app.

However, if you do not install the CLT explicitly, you will miss some
files such as the infamous tclConfig.sh that is required to build
MacPorts itself.

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev