Mon Jul 16 15:05:11 PDT 2007
ec.de> <slrnf9nq2t.1fr5.steve at brandy.dedrat.com>
From: Matthew Dillon <dillon at apollo.backplane.com>
Subject: Re: [issue730] Latest DEVEL still reflects old pkg_* paths
Date: Mon, 16 Jul 2007 15:04:12 -0700 (PDT)
List-Post: <mailto:bugs at crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request at crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request at crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request at crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs at crater.dragonflybsd.org>
Sender: bugs-errors at crater.dragonflybsd.org
Errors-To: bugs-errors at crater.dragonflybsd.org
X-Trace: 1184623610 crater_reader.dragonflybsd.org 793 188.8.131.52
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:7392
:I mentioned this on IRC but one simple path issue is fixed by
:I am quite confused about versions here I assume this patch was
:commited against the "new" installer (which has proved hard to port
:to Dragonflybsd) rather than the old ("working") installer.
:I'm not even sure where the definitive Dragonflybsd installer repo is?
:And can't help wondering whether it might be simplier to import the old
:installer into the Dragonflybsd CVS tree rather than using pkgsrc or
:the new installer repo? And maybe we should just concentrate on
:testing the old one (with vmware or whatever) and minor bug fixes/patches?
Yes, that's precisely the correct patch and I'll be adding it to my
modified patches/ list for the pkgsrc package soon. Thanks for the
The lua issue is totally separate... the problem there is that we do
not want to have to install a ton of infrastructure JUST to support
the installer, at least not in the base CD distribution.
<dillon at backplane.com>
More information about the Bugs