Subject: Re: port-macppc/29655 (macppc cd-rom image build does notcreatebootable
To: None <port-macppc-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
List: netbsd-bugs
Date: 10/07/2006 19:35:04
The following reply was made to PR port-macppc/29655; it has been noted by GNATS.
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
To: he@NetBSD.org
Cc: gnats-bugs@NetBSD.org, tsutsui@NetBSD.org,
port-macppc-maintainer@NetBSD.org, netbsd-bugs@NetBSD.org,
gnats-admin@NetBSD.org, tsutsui@ceres.dti.ne.jp
Subject: Re: port-macppc/29655 (macppc cd-rom image build does notcreatebootable
cd-rom)
Date: Sun, 8 Oct 2006 04:34:25 +0900
> 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.
My point is:
Why do we have to maintain two independent infrastructures
(src/etc/etc.* and src/distrib/cdrom) for the same iso target?
Isn't it better to modify src/distrib/cdrom/Makefile etc.
to handle iso-image target of build.sh?
---
Izumi Tsutsui