Slash

At 21:40 -0800 2001.02.22, Mike Gholson wrote:
>I didn't do anything with my Perl installation.  I've been using the
>perl package that comes with the Redhat install.  Here's the answer
>to my inquiry about the locate of DB.pm
>
>/usr/local/lib/perl5/5.6.0/DB.pm
>/home/slash/lib/perl5/site_perl/5.005/i386-linux/Slash/DB.pm
>/root/slash-1.1.4-bender/Slash/DB/DB.pm
>/root/slash-1.1.4-bender/Slash/blib/lib/Slash/DB.pm
>
>I ran the make routines as suggested in the help file using the
>INIT and PREFIX lines:
>
>make INIT=/etc/rc.d PREFIX=/home/slash
>make install INIT=/etc/rc.d PREFIX=/home/slash
>
>Any clue?

Yes.

I think what happened is that we didn't think through this well enough.
Part of it may be that one or all of us are not very clued on Makefiles.
At least, I know I am not.  To the point: we use PREFIX to say where to
install the slash directory, normally set to /usr/local/slash/.  Perl uses
PREFIX to say where to install the modules.  Apparently, the PREFIX gets
passed down to the Perl Makefiles (duh, I suppose).  Solution: I think we
should use something other than PREFIX for /usr/local/slash.

I can fix this, I think.  Although I am not sure if this will fix the
problem, exactly.  I am concerned that perhaps not all the scripts will
work properly with PREFIX of other than /usr/local/slash.  So here is my
idea: please go back to your slash installation directory.  Do "cd Slash".
Then do "perl Makefile.PL".  Then do "make", and "make install".  This
should install the modules in the correct place.

Then please test everything out (what you can; especially stuff like
install-slashsite, slashd, portald, etc.) and report back; if it works for
you, then the fix is just to change PREFIX to something else.

I am sorry for asking to put this burden on you, but I do not have time in
the next few days to set up and test a new install; if you don't get a
chance, that's OK; I can try sometime next week.

Thanks,

-- 
Chris Nandor                      pudge@...    http://pudge.net/
Open Source Development Network    pudge@...     http://osdn.com/

On Fri, 23 Feb 2001, Chris Nandor wrote:

> I think what happened is that we didn't think through this well enough.
> Part of it may be that one or all of us are not very clued on Makefiles.
> At least, I know I am not.  To the point: we use PREFIX to say where to
> install the slash directory, normally set to /usr/local/slash/.  Perl uses
> PREFIX to say where to install the modules.  Apparently, the PREFIX gets
> passed down to the Perl Makefiles (duh, I suppose).  Solution: I think we
> should use something other than PREFIX for /usr/local/slash.

This would explain and confirm a weird problem I had too, with all the
bender perl modules being installed in /usr/local/slash/lib/perl5 .  I
moved the files into the right places by hand, assuming I had bungled
something.

Chris,

The instructions worked, however, slash is still giving me
problems when running install-slashsite.

See below.

> -----Original Message-----
> From: Chris Nandor [mailto:pudge@...]
> 
> I can fix this, I think.  Although I am not sure if this will fix the
> problem, exactly.  I am concerned that perhaps not all the 
> scripts will
> work properly with PREFIX of other than /usr/local/slash.  So 
> here is my
> idea: please go back to your slash installation directory.  
> Do "cd Slash".
> Then do "perl Makefile.PL".  Then do "make", and "make install".  This
> should install the modules in the correct place.
-----------------

perl Makefile.PL -- success
make             -- success
make install     -- success


> Then please test everything out (what you can; especially stuff like
> install-slashsite, slashd, portald, etc.) and report back; if 
> it works for
> you, then the fix is just to change PREFIX to something else.
------------------

install-slashsite -- fails (see below)

[root@... bin]# ./install-slashsite
Can't locate XML/Parser.pm in @INC (@INC
contains: /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503
/usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005
.) at /usr/lib/perl5/site_perl/5.005/i386-linux/Slash/Utility.pm line 36.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.005/i386-linux/Slash/Utility.pm line 36.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.005/i386-linux/Slash/DB/Utility.pm line 9.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.005/i386-linux/Slash/DB.pm line 10.
BEGIN failed--compilation aborted at ./install-slashsite line 11.
[root@... bin]# 


slashd start -- fails (see below)

NOT Starting slashd: No /usr/local/slash/slash.sites


> I am sorry for asking to put this burden on you, but I do not 
> have time in
> the next few days to set up and test a new install; if you don't get a
> chance, that's OK; I can try sometime next week.
------------------

No problem.  I'm a QA engineer during the week.  So, this kind of
testing doesn't bother me.  If you need me to do more, please let
me know.  Although, I am still very new to slash. :)

-- Mike Gholson

At 10:52 -0800 2001.02.25, Mike Gholson wrote:
>perl Makefile.PL -- success
>make             -- success
>make install     -- success

Good.


>> Then please test everything out (what you can; especially stuff like
>> install-slashsite, slashd, portald, etc.) and report back; if
>> it works for
>> you, then the fix is just to change PREFIX to something else.
>------------------
>
>install-slashsite -- fails (see below)
>
>[root@... bin]# ./install-slashsite
>Can't locate XML/Parser.pm in @INC (@INC
>contains: /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503
>/usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005
>.) at /usr/lib/perl5/site_perl/5.005/i386-linux/Slash/Utility.pm line 36.

Is XML::Parser installed?


>slashd start -- fails (see below)
>
>NOT Starting slashd: No /usr/local/slash/slash.sites

I believe slash.sites is created when the site is created.  If
install-slashsite does not create a site, there are no sites for slashd to
run against.


>No problem.  I'm a QA engineer during the week.  So, this kind of
>testing doesn't bother me.  If you need me to do more, please let
>me know.  Although, I am still very new to slash. :)

:)  Thanks.  It looks like it is all OK, except for the lack of
XML::Parser.  It could be that when you ran Bundle::Slash, you did not have
expat installed, so XML::Parser failed.  Re-run the install of
Bundle::Slash (it will safely skip anything already installed).  See the
note in INSTALL about expat.

Thanks,

-- 
Chris Nandor                      pudge@...    http://pudge.net/
Open Source Development Network    pudge@...     http://osdn.com/

Chris (and others watching),

Here's the latest on this venture.  Apologies for the delay.


> -----Original Message-----
> From: Chris Nandor [mailto:pudge@...]
> 
> At 10:52 -0800 2001.02.25, Mike Gholson wrote:
> >perl Makefile.PL -- success
> >make             -- success
> >make install     -- success
> 
> Good.
> 
> 
> >> Then please test everything out (what you can; especially 
> stuff like
> >> install-slashsite, slashd, portald, etc.) and report back; if
> >> it works for
> >> you, then the fix is just to change PREFIX to something else.
> >------------------
> >
> >install-slashsite -- fails (see below)
> >
> >[root@... bin]# ./install-slashsite
> >Can't locate XML/Parser.pm in @INC (@INC
> >contains: /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503
> >/usr/lib/perl5/site_perl/5.005/i386-linux 
> /usr/lib/perl5/site_perl/5.005
> >.) at 
> /usr/lib/perl5/site_perl/5.005/i386-linux/Slash/Utility.pm line 36.
> 
> Is XML::Parser installed?
---------------

It was trying to install.  But, it saw errors.


> >slashd start -- fails (see below)
> >
> >NOT Starting slashd: No /usr/local/slash/slash.sites
> 
> I believe slash.sites is created when the site is created.  If
> install-slashsite does not create a site, there are no sites 
> for slashd to
> run against.
--------------

Yep.


> :)  Thanks.  It looks like it is all OK, except for the lack of
> XML::Parser.  It could be that when you ran Bundle::Slash, 
> you did not have
> expat installed, so XML::Parser failed.  Re-run the install of
> Bundle::Slash (it will safely skip anything already 
> installed).  See the
> note in INSTALL about expat.
-----------------

I tried to install Bundle::Slash and kept failing during the 
XML section.  Kept seeing the 'missing parser.pm @INC' error.

I then tried a manual install of XML-Parser from the link supplied
in the Install doc: http://search.cpan.org/search?dist=XML-Parser

That failed because it needed expat.  So, that was downloaded
from SourceForge.

Cutting story short:  After installing these two packages manually,
the install-slashsite file worked w/out error.

My opinion:  Using CPAN wasn't working correctly.  Upon manual
install of the files, it seems to be working.  Could it be my
selection of CPAN download sites?  Possibly timing out or lack
of all CPAN modules?  What's a good CPAN site to use for the
Slash distribution files?

[m]

Mike Gholson wrote:

> My opinion:  Using CPAN wasn't working correctly.  Upon manual
> install of the files, it seems to be working.

Well, more exactly is the dependance of a CPAN module (XML::Parser) upon
a non-Perl component as expat. So, you positively first need to install
expat.

This may be better explained in the INSTALL docs (including URLs for
expat), while we wait for major distributions to include it by default,
if ever.

-- 
Alessio F. Bragadini		alessio@...
APL Financial Services		http://village.albourne.com
Nicosia, Cyprus		 	phone: +357-2-755750

"It is more complicated than you think"
		-- The Eighth Networking Truth from RFC 1925

At 23:41 -0800 2001.02.28, Mike Gholson wrote:
>I then tried a manual install of XML-Parser from the link supplied
>in the Install doc: http://search.cpan.org/search?dist=XML-Parser
>
>That failed because it needed expat.  So, that was downloaded
>from SourceForge.

Yes, this is noted in the INSTALL.  Perhaps not prominently enough, though.


>Cutting story short:  After installing these two packages manually,
>the install-slashsite file worked w/out error.

Good.


>My opinion:  Using CPAN wasn't working correctly.  Upon manual
>install of the files, it seems to be working.  Could it be my
>selection of CPAN download sites?  Possibly timing out or lack
>of all CPAN modules?  What's a good CPAN site to use for the
>Slash distribution files?

I am not sure, as I don't know what problem you were having with CPAN.


At 10:38 +0200 2001.03.01, Alessio Bragadini wrote:
>This may be better explained in the INSTALL docs (including URLs for
>expat), while we wait for major distributions to include it by default,
>if ever.

There is a URL for expat in INSTALL.  But it is toward the end, where the
required modules are listed, not in the part about using CPAN.pm.

-- 
Chris Nandor                      pudge@...    http://pudge.net/
Open Source Development Network    pudge@...     http://osdn.com/

> -----Original Message-----
> From: Alessio Bragadini [mailto:alessio@...]
>
> Well, more exactly is the dependance of a CPAN module 
> (XML::Parser) upon
> a non-Perl component as expat. So, you positively first need 
> to install
> expat.
----------------

Yes, after installing expat, things moved forward.  But, I don't
remember seeing a section about the manual install of expat in the
installation instructions.  I'm using a combination of two instructions
- one from the tarball distribution and the other from bender.  I
definately like the bender-install method.

This leads me to the next question.

Why two installations?  Why doesn't slash come default with the source
code for all installations?  Seems like that would be easier to support.



> This may be better explained in the INSTALL docs (including URLs for
> expat), while we wait for major distributions to include it 
> by default, if ever.
---------------

My lack of understanding about the distribution process through CPAN
prevents me from coming up with a valid point on this.  But, what does
it take to add something like this to your Bundle::Slash module?

-- Mike

At 08:57 -0800 2001.03.01, Mike Gholson wrote:
>Yes, after installing expat, things moved forward.  But, I don't
>remember seeing a section about the manual install of expat in the
>installation instructions.  I'm using a combination of two instructions
>- one from the tarball distribution and the other from bender.  I
>definately like the bender-install method.

It is in the bender INSTALL.  It is under REQUIREMENTS.  Grep for "expat"
if you don't believe me.  :-)  I've added a note under the section
describing the CPAN installation to remind you to look at REQUIREMENTS.


>This leads me to the next question.
>
>Why two installations?  Why doesn't slash come default with the source
>code for all installations?  Seems like that would be easier to support.

I am not sure what you are referring to by "two installations".


>> This may be better explained in the INSTALL docs (including URLs for
>> expat), while we wait for major distributions to include it
>> by default, if ever.
>---------------
>
>My lack of understanding about the distribution process through CPAN
>prevents me from coming up with a valid point on this.  But, what does
>it take to add something like this to your Bundle::Slash module?

It cannot be done, unless I write my own module that builds and installs
expat, which I am not going to do.  :)

-- 
Chris Nandor                      pudge@...    http://pudge.net/
Open Source Development Network    pudge@...     http://osdn.com/