Martin MC Brown wrote:
>
>
> But where on the filesystem does SUNWmysql35o deliver its content
> (this is why it's useful to have some listing or Appendix showing
> what each package delivers)?
>
It will be listed under the 5.0 release, but to use the Connector/ODBC
yo
Jyri Virkki wrote:
> Jan S Berg wrote:
>
>>
>>> But where on the filesystem does SUNWmysql35o deliver its content
>>> (this is why it's useful to have some listing or Appendix showing
>>> what each package delivers)?
>>>
>> It will be listed under the 5.0 release, but to use the Conn
Martin MC Brown wrote:
> On 20 Feb 2008, at 19:26, Matt.Ingenthron at Sun.COM wrote:
>
>
>> Jyri Virkki wrote:
>>
>>> Matt Ingenthron wrote:
>>>
>>>
I believe we'll need to deliver both, and there are probably still a
number of reasons (for now) that one may choose to run 3
But where on the filesystem does SUNWmysql35o deliver its content
(this is why it's useful to have some listing or Appendix showing
what each package delivers)?
>>> It will be listed under the 5.0 release, but to use the Connector/
>>> ODBC
>>> you will specify how to con
On 20 Feb 2008, at 19:26, Matt.Ingenthron at Sun.COM wrote:
> Jyri Virkki wrote:
>> Matt Ingenthron wrote:
>>
>>> I believe we'll need to deliver both, and there are probably still a
>>> number of reasons (for now) that one may choose to run 32-bit even
>>> on a
>>> system with a 64-bit ISA, wh
> What would concern me is the guy evaluating OpenSolaris, grabbing an
> extension that's needed for his application, running
> gem/apxs/phpize/pecl and then seeing it blow up. The install readme
> won't likely have an "if you're on OpenSolaris" branch, and it may not
> even be clear where the pr
