Mac::Growl?

[Bradley Giesbrecht]

On May 1, 2010, at 9:42 AM, Steve Morris wrote:

> Brad,
>
> The install worked (didn't give an error) but the install didn't run
> the test suite so I am not sure that what was installed worked. This
> package comes with a bunch of tests. Also I know that Mac::Growl has a
> bunch of dependencies on other CPAN packages but I had already
> installed the p5- versions of those so dependencies  didn't get
> tested. "port deps p5-mac-growl" doesn't list any dependancies so this
> is probably a problem. I know at a minimum it depends on Mac::Glue and
> some Applescript stuff. These should have been listed.

I only saw a dep for mac:glue and that was only if you were using  
mac::glue. Other then that I didn't see anything in the docs I read  
about deps.


> Other general development questions:
>
> I'll save this email for future reference. You suggest that I could
> have built it in the port directory without running portindex. That
> sounds like it could be useful. How would that work?

cd to where your Portfile is and you can use the port command without  
including the port.

cd ~/ports/perl/p5-mac-growl
port info
sudo port extract
ls ./work
sudo port patch
sudo port configure
sudo port build
sudo port destroot
ls ./work/destroot

I just listed some of the port stages for your reference. Each stage  
will call all previous stages.

There is a file in ./work named .macports.<port name>.state that keeps  
track of what stages have been completed. Every time you make a change  
to your portfile ./work gets replaced. If you want to prevent this  
behaviour because your extract is heavy or what ever you can do "port - 
vof patch" or what ever and port will ignore the fact the your  
Portfile is newer then your state file.

It's not necessary to sudo all the commands but it you don't the the  
worksrcpath is relevant to ~/.macports or something and I prefer to  
have ./work in the port dir. Makes patching easier for me. I get tired  
of sudo and just sudo -s. I'm bad, as in not good not as in badass.


> cpan2port isn't in my path and "port search cpan2port" doesn't find
> it. Is it part of macports? Lots of tickets reference it but the wiki
> search doesn't seem to find any documentation. What am I missing?

cpan2port is in http://svn.macports.org/repository/macports/contrib/.


> Thanks for the help.
>
> Steve
>
> PS. Next time I'll remember cpan2port and try it myself before asking.
>
> On Sat, May 1, 2010 at 11:34 AM, Bradley Giesbrecht  
> <brad at pixilla.com> wrote:
>>
>> On May 1, 2010, at 8:18 AM, Steve Morris wrote:
>>
>>> Thanks Brad,
>>>
>>> I'm trying but I am new at this. I apologize but I need a little  
>>> more
>>> info than the local-repositories guide and the ticket offers. I  
>>> edited
>>> sources.conf, and created a ~/ports directory to match the URL I  
>>> added
>>> but I don't know what to put inside that directory. Presumably the
>>> Portfile in the ticket you created but where does it go? Which
>>> subdirectory do I create for it? And what is the port command do I
>>> need to use it. I'm guessing "port install p5-mac-growl"?
>>>
>>> Steve
>>>
>>>> http://trac.macports.org/ticket/24748
>>>>
>>>> Steve, if you don't already have a local repo to try out this  
>>>> port look
>>>> here
>>>> to learn how to set one up:
>>>> http://guide.macports.org/#development.local-repositories
>>
>> Easy.
>>
>> port search p5-*
>>
>> This will give you a list of all the p5 (perl modules) in macports.
>>
>> Picking one of them lets see what category macports keeps p5's in.
>>
>> port dir p5-algorithm-annotate
>>
>> Now cd to your local repo and create your category and port dir.
>>
>> cd ~/ports
>> mkdir -p perl/p5-mac-growl
>>
>>
>> Now cd to your port dir and grab the file. I'm choosing to use curl  
>> but how
>> ever you want to get it there is fine.
>> cd perl/p5-mac-growl
>> curl http://trac.macports.org/raw-attachment/ticket/24748/Portfile -O
>>
>> Now you could just build the port while in the port dir but for the  
>> sake of
>> learning lets let port know about our new port.
>> cd ~/ports
>> portindex
>> port dir p5-mac-grow
>>
>> Now that port is aware of your new port you can install it as any  
>> other
>> port.
>> port install p5-mac-grow
>>
>>
>> // Brad
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20100501/d2088b69/attachment.html>