On Tue, October 20, 2009 6:50 am, Hasso Tepper wrote:
> 鈏el kenal p輑val (teisip輑v 20 oktoober 2009) kirjutas Hasso Tepper:
>> Justin C. Sherrill wrote:
>> > Has the logs from the build - parrot, for instance, failed because of
>> > a plist error, so that's an easy fix.
>>
>> PLIST errors are often very far from being trivial to fix - invloving
>> solving issues with different platforms or setups installing different
>> files etc.
>
> The very same lang/parrot is a good example - it's not "let's just add
> missing files into PLIST" issue, but "let's find out why shared library
> are not built on some platforms (notably NetBSD)" issue.
Well, I hoped it was easy... Parrot is on a monthly development cycle, so
I expect some problems to crop up. I sent a note to the package
maintainer.
Should build problems generally be addressed by filing reports in NetBSD's
GNATS, especially for packages where the owner is pkgsrc-users@netbsd.org?
I've had good luck mailing maintainers directly, but that's more because
of good maintainers than the process itself.