head	1.2;
access;
symbols
	pkgsrc-2026Q1:1.2.0.26
	pkgsrc-2026Q1-base:1.2
	pkgsrc-2025Q4:1.2.0.24
	pkgsrc-2025Q4-base:1.2
	pkgsrc-2025Q3:1.2.0.22
	pkgsrc-2025Q3-base:1.2
	pkgsrc-2025Q2:1.2.0.20
	pkgsrc-2025Q2-base:1.2
	pkgsrc-2025Q1:1.2.0.18
	pkgsrc-2025Q1-base:1.2
	pkgsrc-2024Q4:1.2.0.16
	pkgsrc-2024Q4-base:1.2
	pkgsrc-2024Q3:1.2.0.14
	pkgsrc-2024Q3-base:1.2
	pkgsrc-2024Q2:1.2.0.12
	pkgsrc-2024Q2-base:1.2
	pkgsrc-2024Q1:1.2.0.10
	pkgsrc-2024Q1-base:1.2
	pkgsrc-2023Q4:1.2.0.8
	pkgsrc-2023Q4-base:1.2
	pkgsrc-2023Q3:1.2.0.6
	pkgsrc-2023Q3-base:1.2
	pkgsrc-2023Q2:1.2.0.4
	pkgsrc-2023Q2-base:1.2
	pkgsrc-2023Q1:1.2.0.2
	pkgsrc-2023Q1-base:1.2;
locks; strict;
comment	@# @;


1.2
date	2023.01.27.23.22.31;	author thorpej;	state Exp;
branches;
next	1.1;
commitid	9EYqkHVAg5OTFebE;

1.1
date	2023.01.20.21.43.56;	author thorpej;	state Exp;
branches;
next	;
commitid	CEkOKsGhlFShmkaE;


desc
@@


1.2
log
@Fix a bug in "?label" expression evaluation, which caused those expressions
to result in an "non-existent label" error when testing for the existence
of a label that does not yet exist (which is the whole point of that
expression).

Bump PKGREVISION to 1.
@
text
@$NetBSD: distinfo,v 1.1 2023/01/20 21:43:56 thorpej Exp $

BLAKE2s (z80asm-1.8.tar.gz) = c20093c5cce1121728b3deb795136402429fda251a101a533f0d4434019ccdfd
SHA512 (z80asm-1.8.tar.gz) = 0b2da513200dbdd2d4867347b24488c786e014e4ab84e92e8f0585971bb39a57e65409dc6a95edbe9c017ebb3b25b4b4be9a7bd436b6cf610b59d46a711cb66f
Size (z80asm-1.8.tar.gz) = 57269 bytes
SHA1 (patch-Makefile) = 3b3c85d4005ea5e8dc5ee910f854e46b1b8f7b0a
SHA1 (patch-expressions.c) = ae8242f40b38a77cb7642f1bed52db58a1ed0a86
SHA1 (patch-z80asm.c) = d5abe41d337a738ec41bae19c2d68262dca04339
@


1.1
log
@Add a package for z80asm, a Z80 assembler.

This is distinct from the other z80-asm package.  Why do we have it, then?
Because this Z80 assebler has some features that the z80-asm assembler
does not.
@
text
@d1 1
a1 1
$NetBSD$
d7 1
a7 1
SHA1 (patch-expressions.c) = c44284596a5278b347707dda5fe8fa85a98030cc
@