head	1.4;
access;
symbols
	pkgsrc-2026Q1:1.4.0.6
	pkgsrc-2026Q1-base:1.4
	pkgsrc-2025Q4:1.4.0.4
	pkgsrc-2025Q4-base:1.4
	pkgsrc-2025Q3:1.4.0.2
	pkgsrc-2025Q3-base:1.4
	pkgsrc-2025Q2:1.3.0.4
	pkgsrc-2025Q2-base:1.3
	pkgsrc-2025Q1:1.3.0.2
	pkgsrc-2025Q1-base:1.3;
locks; strict;
comment	@# @;


1.4
date	2025.08.13.11.07.00;	author pho;	state Exp;
branches;
next	1.3;
commitid	oGqtJTKdyCfCKy6G;

1.3
date	2025.03.05.03.39.31;	author pho;	state Exp;
branches;
next	1.2;
commitid	VPkRDaZT4MoYrPLF;

1.2
date	2025.02.02.13.05.25;	author pho;	state Exp;
branches;
next	1.1;
commitid	Zl7FwsffomOQzTHF;

1.1
date	2025.01.31.14.35.08;	author pho;	state Exp;
branches;
next	;
commitid	azXYmA1X1Ot49EHF;


desc
@@


1.4
log
@Bump all Haskell because lang/ghc910 has got a library change
@
text
@# $NetBSD: Makefile,v 1.3 2025/03/05 03:39:31 pho Exp $

DISTNAME=	tasty-expected-failure-0.12.3
PKGREVISION=	3
CATEGORIES=	devel

MAINTAINER=	pkgsrc-users@@NetBSD.org
COMMENT=	Mark tasty tests as failure expected
LICENSE=	mit

.include "../../devel/hs-tagged/buildlink3.mk"
.include "../../devel/hs-tasty/buildlink3.mk"
.include "../../devel/hs-unbounded-delays/buildlink3.mk"
.include "../../mk/haskell.mk"
.include "../../mk/bsd.pkg.mk"
@


1.3
log
@recursive revbump after patching lang/ghc910
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.2 2025/02/02 13:05:25 pho Exp $
d4 1
a4 1
PKGREVISION=	2
@


1.2
log
@Bump all Haskell packages after switching the default compiler.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.1 2025/01/31 14:35:08 pho Exp $
d4 1
a4 1
PKGREVISION=	1
@


1.1
log
@devel/hs-tasty-expected-failure: import hs-tasty-expected-failure-0.12.3

With the function Test.Tasty.ExpectedFailure.expectFail in the provided module
Test.Tasty.ExpectedFailure, you can mark that you expect test cases to fail, and
not to pass.

This can for example be used for test-driven development: Create the tests, mark
them with Test.Tasty.ExpectedFailure.expectFail, and you can still push to the
main branch, without your continuous integration branch failing.

Once someone implements the feature or fixes the bug (maybe unknowingly), the
test suite will tell him so, due to the now unexpectedly passing test, and he
can remove the Test.Tasty.ExpectedFailure.expectFail marker.

The module also provides Test.Tasty.ExpectedFailure.ignoreTest to avoid running
a test. Both funtions are implemented via the more general
Test.Tasty.ExpectedFailure.wrapTest, which is also provided.
@
text
@d1 1
a1 1
# $NetBSD$
d4 1
@