p5 modules, get me started on one

Bryan Blackburn blb at macports.org
Mon Jan 19 18:50:55 PST 2009


On Mon, Jan 19, 2009 at 05:54:53PM -0800, Scott Haneda said:
> On Jan 19, 2009, at 5:31 PM, Bryan Blackburn wrote:
>
>> On Mon, Jan 19, 2009 at 05:11:44PM -0800, Scott Haneda said:
>>> Hello, I need a little help.
>
>> You'll want to have this under /Users/me/macports/perl/p5-file- 
>> readbackwards
>> as this is in the perl category, and as mentioned above, will be named
>> p5-file-readbackwards.
>>
>> [1] - <http://guide.macports.org/#reference.portgroup.perl>
>>
>>> Given the above example port file, where is it being told to  
>>> download?  I
>>> can not seem to locate a file, so I must be misunderstanding this  
>>> `sudo
>>> find /opt/ -name "perl5.setup"`
>
>
> /Users/me/macports/perl
>
> -rw-r--r--  1 me  wheel    0 Jan 19 17:50 PortIndex
> -rw-r--r--  1 me  staff  284 Jan 19 17:50 p5-file-readbackward
>
> $portindex
> Creating software index in /Users/me/macports/perl
>
> Total number of ports parsed:	0
> Ports successfully parsed:	0	
> Ports failed:			0
>
> cat p5-file-readbackward

Actually, p5-file-readbackward should be a directory, and what you have in
this file should actually be called Portfile; so you'd end up with
/Users/me/macports/perl/p5-file-readbackward/Portfile.

> # $Id$
> PortSystem 1.0
> PortGroup perl5 1.0
>
> perl5.setup             File::ReadBackwards 1.04
> maintainers             nomaintainer
> description             test of port file readbackwards
> long_description        This module provides things that are useful
> platforms               darwin
>
> * How come other ports of this nature do not use :: and use - ?

Oops, my mistake, that should be File-ReadBackwards instead of using the
'::'.

>
> sudo port install p5-file-readbackwards
> Warning: Can't open index file for source: file:///Users/me/macports
> Error: Port p5-file-readbackwards not found

When first developing a port it's simplest to be in the port's directory
(/Users/me/macports/perl/p5-file-readbackward in this case); that way you
can run the port commands without a port name, like

$ sudo port -d install
$ port lint

and any other commands.  This causes port to look in the current dir for a
Portfile, so you can be sure you're using what's there and not something
else.
Also, when developing a port, I seriously strongly suggest using -d so you
can watch what's going on.

Bryan


>
> Any suggestions?
> --
> Scott


More information about the macports-users mailing list