MacPorts php5 used to use Mac OS X's libiodbc, until, in the process of
separating functionality from the php5 port into separate ports, I realized we
were doing that. Since our policy (see FAQ) is to use libraries provided by
MacPorts, not those provided by Mac OS X, I used unixODBC, since we d
I am new to php and ODBC so I have no experience with either.
However, according to http://support.openlinksw.com/support/mac-faq.html#7
libiodbc is what Apple has been using since Jaguar and is what is in /
usr/lib on my Leopard system.
On Aug 2, 2010, at 5:40 PM, Ryan Schmidt wrote:
On
On Aug 2, 2010, at 17:25, dlc wrote:
> I want to setup php hosting in virtuoso which works with libiodbc instead of
> unixODBC. Should a variant of php5-odbc be made or should this be a new php5
> port?
It should be a variant of the php5-odbc port, since in both cases it is the php
odbc modul
I want to setup php hosting in virtuoso which works with libiodbc
instead of unixODBC. Should a variant of php5-odbc be made or should
this be a new php5 port?
thanks
David Coate
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http:/
On Aug 2, 2010, at 15:19, joc...@macports.org wrote:
> Revision: 70225
> http://trac.macports.org/changeset/70225
> Author: joc...@macports.org
> Date: 2010-08-02 13:19:27 -0700 (Mon, 02 Aug 2010)
> Log Message:
> ---
> follow stelath maintainer upgrade
>
> Modified Paths:
On Aug 2, 2010, at 11:46, David Baumgold wrote:
> Ryan, can you instruct us on the proper way to write a select port, now that
> the select functionality is built into Macports?
I'm afraid I haven't looked into it, I just remember hearing on the list about
its existence.
I'm fine with all of that. Kimura, do you want to be the maintainer of the
ruby_select port? Ryan, can you instruct us on the proper way to write a
select port, now that the select functionality is built into Macports?
On Mon, Aug 2, 2010 at 10:18 AM, kimura wataru wrote:
> Hi all,
>
> I agree w
Please join us in welcoming the following new MacPorts committers:
- Michael Feiri (mfeiri)
We look forward to continued excellent contributions from these new team
members.
- Bryan, Joshua, Rainer, and Ryan
Do you want to join the MacPorts team? If you would like to be
considered for team me
Hi all,
I agree we need "ruby_select".
If you allow the following plan, I'll work for this.
step1 (introduce ruby_select)
* add port:ruby_select
* add suffix to port:ruby (1.8.7) and port:ruby186 (1.8.6)
* remove the variant "nosuffix" from port:ruby19
step2 (deprecate port:ruby and add po
Should we include dependencies for a port if they are only used during the test
phase?
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.c
Ah, you're right...
Index: Portfile
===
--- Portfile(revision 70213)
+++ Portfile(working copy)
@@ -114,7 +114,7 @@
set i [lsearch -exact ${pythons_ports} ${p}]
set c [lreplace ${pythons_ports} ${i} ${i}]
eval
On 2010-08-02 07:48 , Jeremy Huddleston wrote:
> From the Portfile:
>
> foreach s ${pythons_suffixes} {
> set p python${s}
> set v [string index ${s} 0].[string index ${s} 1]
> set i [lsearch -exact ${pythons_ports} ${p}]
> set c [lreplace ${pythons_ports} ${i} ${i}]
> eval
12 matches
Mail list logo
