Any haskell port should have a depends_build and depends_run for port:ghc.
But there is no library to link against in ghc, so it should not be a
depends_lib.
The depends_run is needed by the post-activate bits.
Le 19 mars 2010 à 13:55, Ryan Schmidt a écrit :
> On Mar 19, 2010, at 07:48, Gregory Wright wrote:
>> On 3/19/10 6:08 AM, Ryan Schmidt wrote:
>>> I see you adding these things to a lot of haskell ports. Is it perhaps
>>> appropriate to make the haskell portgroup do this automatically?
>>
>> I have no objection to this. The "-v" is just to generate verbose output,
>> so there
>> is something to look at when port is run with "-d" or "-v".
>>
>> The --with-ghc=${configure.cc} is always needed to prevent the cabal library
>> (which does the configure, build and install work) from using the first thing
>> name "gcc" on the $PATH.
>>
>> And there won't be universal variants of haskell ports any time soon.
>
> Ok, feel free to make the changes to the haskell portgroup then.
>
> I also noticed you adding "depends_lib port:ghc" to many haskell ports. The
> haskell portgroup already adds "depends_build port:ghc" but if depends_lib is
> more appropriate, maybe that should be changed in the portgroup too.
>
> You're probably one of the most qualified people to make changes to that
> portgroup, since you know about haskell things, so feel free to make whatever
> changes you feel are appropriate. The portgroups are there to factor common
> code out of ports, so if you find you're repeating yourself in portfiles,
> it's probably time to move the repetitive code to the portgroup.
>
>
> _______________________________________________
> macports-dev mailing list
> [email protected]
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
