Re: DBD::mysql question

2011-10-30 Thread Joshua Root
On 28164-7-23 05:59 , Ryan Schmidt wrote:
 On Oct 29, 2011, at 08:11, Mr. Puneet Kishor wrote:
 
 Instead, for the most part, when it comes to perl modules, just install them 
 using cpan or cpanminus (I prefer cpanminus). As long as your macport 
 preferred perl is the default perl in the path, your requested module will 
 get installed correctly.
 
 If you use MacPorts, you shouldn't use CPAN to install modules; they'll 
 conflict with MacPorts ports of those modules. If ports don't exist for the 
 modules you need, request them, or even create them yourself and submit them; 
 the cpan2port script makes it pretty easy to create ports for perl modules.

I'm not very familiar with CPAN, but if it can be configured to install
somewhere other than the default location, that would be fine. We should
really modify its defaults so using it won't cause conflicts with p5
ports. Same goes for similar tools for other languages like
easy_install/pip, gem, and so on.

- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-30 Thread Ryan Schmidt

On Oct 30, 2011, at 21:29, Daniel J. Luke wrote:

 On Oct 30, 2011, at 5:23 PM, Joshua Root wrote:
 I'm not very familiar with CPAN, but if it can be configured to install
 somewhere other than the default location, that would be fine. We should
 really modify its defaults so using it won't cause conflicts with p5
 ports. Same goes for similar tools for other languages like
 easy_install/pip, gem, and so on.
 
 
 The way things work now:
 
 we install into a vendor_perl directory, cpan installs into a 'site' (local) 
 directory.
 
 If you install a macports module and the same module from cpan, they both 
 install (into their own directories).
 
 The way we have macports perl configured, it will search your site (local) 
 directory, then the vendor directory, then the directory where all the stuff 
 that ships with perl lives.
 
 This means, that your site (local/cpan) installed modules will override what 
 macports installs (which may or may not be what you want).

Ok, that's actually better than I anticipated. :)

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


DBD::mysql question

2011-10-29 Thread Phil Dobbin

Hi.

I’m trying to install p5.12-dbd-mysql but it starts to 
download MySQL 5 with a view, I should imagine, to install that first.


Seeing as I’ve rolled my own MySQL what’s the syntax to port 
install p5.12-dbd-mysql without MySQL? Is it sudo port install 
p5.12-dbd-mysql -mysql5?


Any help appreciated,

Cheers,

Phil.
--
Please consider the environment before reading this email...

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-29 Thread Ryan Schmidt

On Oct 29, 2011, at 05:50, Phil Dobbin wrote:

 Seeing as I’ve rolled my own MySQL what’s the syntax to port install 
 p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql 
 -mysql5?

As far as I know, DBD::MySQL requires the MySQL libraries, and MacPorts won't 
use the MySQL you compiled yourself.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-29 Thread Mr. Puneet Kishor

On Oct 29, 2011, at 5:50 AM, Phil Dobbin wrote:

 Hi.
 
 I’m trying to install p5.12-dbd-mysql but it starts to download MySQL 5 with 
 a view, I should imagine, to install that first.
 
 Seeing as I’ve rolled my own MySQL what’s the syntax to port install 
 p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql 
 -mysql5?
 


I could be wrong, but I think if a port depends on another port (as described 
in its portfile), you are kinda out of luck --- the dependency will get 
installed. That is why I have a couple of three different perls now on my 
computer, and a few other superfluous software packages.

Instead, for the most part, when it comes to perl modules, just install them 
using cpan or cpanminus (I prefer cpanminus). As long as your macport preferred 
perl is the default perl in the path, your requested module will get installed 
correctly.

--
Puneet Kishor

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-29 Thread Phil Dobbin

On 29/10/11 at 14:03, ryandes...@macports.org (Ryan Schmidt) wrote:


On Oct 29, 2011, at 05:50, Phil Dobbin wrote:

Seeing as I’ve rolled my own MySQL what’s the syntax to 
port install p5.12-dbd-mysql without MySQL? Is it sudo port 
install p5.12-dbd-mysql -mysql5?


As far as I know, DBD::MySQL requires the MySQL libraries, and 
MacPorts won't use the MySQL you compiled yourself.


I just wondered because DBI installed fine from MacPorts. But 
looking back at the copy of my install of DBD::mysql I had to 
explicity add flags for perl to find the MySQL libs  includes 
at compile time (this with perl 5.14  DBD::mysql in usr/local/) 
so maybe not...


Cheers,

Phil.
--
Please consider the environment before reading this email...

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-29 Thread Phil Dobbin

On 29/10/11 at 14:11, punk.k...@gmail.com (Mr. Puneet Kishor) wrote:

[snip]

Instead, for the most part, when it comes to perl modules, just 
install them using cpan or cpanminus (I prefer cpanminus). As 
long as your macport preferred perl is the default perl in the 
path, your requested module will get installed correctly.


Hi, Puneet.

I think I’ll have to stick with version of  DBD::mysql I 
installed in /usr/local/ as I don’t really want to link to 
MySQL libs  includes that are not in /opt/local/


Cheers,

Phil.

--
Please consider the environment before reading this email...

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-29 Thread Ryan Schmidt
On Oct 29, 2011, at 10:08, Phil Dobbin wrote:

 On 29/10/11 at 14:03, ryandes...@macports.org (Ryan Schmidt) wrote:
 
 On Oct 29, 2011, at 05:50, Phil Dobbin wrote:
 
 Seeing as I’ve rolled my own MySQL what’s the syntax to port install 
 p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql 
 -mysql5?
 
 As far as I know, DBD::MySQL requires the MySQL libraries, and MacPorts 
 won't use the MySQL you compiled yourself.
 
 I just wondered because DBI installed fine from MacPorts. But looking back at 
 the copy of my install of DBD::mysql I had to explicity add flags for perl to 
 find the MySQL libs  includes at compile time (this with perl 5.14  
 DBD::mysql in usr/local/) so maybe not...

DBI is the DataBase-Independent module; it doesn't depend on any database 
engine; DBD are the DataBase-Dependent modules; each of them depend on the 
libraries for their respective database engines. You write your abstract 
database-independent perl code to talk to DBI, which then talks to the 
appropriate DBD module to actually talk to the specific database you're using.

Two questions for you...

1. Why did you compile your MySQL server yourself? Why not use the MacPorts 
mysql5-server port?

2. Even if you want to continue using your own hand-compiled MySQL server, 
that's not a problem. p5-dbd-mysql should happily talk to it. In order to do 
so, it will need its own copies of the MySQL libraries, as installed by the 
mysql5 port. So just let MacPorts install the mysql5 port for you, even if you 
don't plan to use it as your server.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-29 Thread Phil Dobbin

On 29/10/11 at 01:22, ryandes...@macports.org (Ryan Schmidt) wrote:


Two questions for you...

1. Why did you compile your MySQL server yourself? Why not use 
the MacPorts mysql5-server port?


I’d originally downloaded  installed the MySQL binary but 
that proved problematical as I’d used the 32-bit version  the 
perl I’d installed in /usr/local/ (not wanting to mess with 
the system perl) was 64-bit therefore they wouldn’t play nice. 
At the time I hadn’t looked at MacPorts (wish I had) mainly 
because in years gone by I’d used Fink  didn’t particularly 
enjoy the experience (YMMV). So I compiled MySQL 64-bit from source.


However, when it came to apache2 I read up on MacPorts  decided 
to try it.


2. Even if you want to continue using your own hand-compiled 
MySQL server, that's not a problem. p5-dbd-mysql should happily 
talk to it. In order to do so, it will need its own copies of 
the MySQL libraries, as installed by the mysql5 port. So just 
let MacPorts install the mysql5 port for you, even if you don't 
plan to use it as your server.


I think that would be the ideal answer as I now have versions of 
apache2, PHP, PEAR  perl from MacPorts  I’m finding MacPorts 
a pleasure to use.


Thanks for all the help, Ryan  everybody else,

Cheers,

Phil.

--
Please consider the environment before reading this email...

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: DBD::mysql question

2011-10-29 Thread Ryan Schmidt

On Oct 29, 2011, at 08:11, Mr. Puneet Kishor wrote:

 I could be wrong, but I think if a port depends on another port (as described 
 in its portfile), you are kinda out of luck --- the dependency will get 
 installed. That is why I have a couple of three different perls now on my 
 computer, and a few other superfluous software packages.

If MacPorts installed the ports for you, in response to a port you asked to 
have installed, then they're not superfluous.

Having multiple perls installed is annoying, I agree. Most ports that use perl 
shouldn't care which perl you use. 5.12 is the version we're defaulting to now 
so that would probably be a safe version to use. 


 Instead, for the most part, when it comes to perl modules, just install them 
 using cpan or cpanminus (I prefer cpanminus). As long as your macport 
 preferred perl is the default perl in the path, your requested module will 
 get installed correctly.

If you use MacPorts, you shouldn't use CPAN to install modules; they'll 
conflict with MacPorts ports of those modules. If ports don't exist for the 
modules you need, request them, or even create them yourself and submit them; 
the cpan2port script makes it pretty easy to create ports for perl modules.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users