The following reply was made to PR port-macppc/29655; it has been noted by GNATS.

From: Havard Eidnes <he@netbsd.org>
To: tsutsui@ceres.dti.ne.jp
Cc: gnats-bugs@netbsd.org, tsutsui@netbsd.org,
	port-macppc-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
	gnats-admin@netbsd.org
Subject: Re: port-macppc/29655 (macppc cd-rom image build does not
 createbootable cd-rom)
Date: Sat, 07 Oct 2006 21:20:47 +0200 (CEST)

 > > Respectfully, I disagree.  I do not understand that there is a
 > > good reason why we make bootable ISO images for some ports for
 > > the setup under src/etc, while for other ports where we know how
 > > to make an ISO image bootable, should *not* do so also for the
 > > image built from src/etc?
 >
 > Non standard tools are required to create bootable cd for macppc,
 > but do you have any idea how to handle them?
 
 That's not really different from the situation for i386, at least
 with respect to the tools used by src/etc for the iso-image
 target, since it uses mkisofs from the cdrtools package, which is
 also "not part of the base tree".  The same situation seems to
 apply to the src/distrib/cdrom/ setup.
 
 However, the "iso-image" target isn't used by any of the
 "release", "build", or "distribution" commands/targets to
 build.sh, so I think that is fine -- if I want to build complete
 bootable iso images, I can install the required package.
 
 > I don't think it's complicated at all:
 > http://mail-index.netbsd.org/port-macppc/2006/10/07/0003.html
 
 Well, it's quite a bit more than doing a "build.sh ... release"
 and follow that with "build.sh ... iso-image", which is what I
 can do for i386.  ...plus using src/distrib/cdrom introduces
 local changes in my source tree, which must be re-done if I want
 to do this for another port.
 
 > > Please re-open the ticket.
 >
 > If you want, feel free to do so by yourself.
 
 I'll take a look.
 
 - H=E5vard