Re: [issue730] Latest DEVEL still reflects old pkg_* paths

[Adrian Michael Nida <nida@xxxxxxxx>]

Quoting Matthew Dillon <dillon@apollo.backplane.com>:

> :After not being able to wake anyone in IRC, I decide to file this 
> bug report in
> :the hopes that the build machine creating the Latest DEVEL can be 
> updated, or I
> :can be told how to fix it for myself.
>
>     Don't worry about it, I'm going start working on the installer
>     for the release tomorrow.  I'll be sure to fix the paths.
>
> 						-Matt


Matt,

Thanks for looking at this.  I'm going to have to reinstall when a replacement
drive arrives (one out of five was DOA), so I'll get a chance soon (hopefully
before you release) to ensure it works.

I've also dropped a message on the bsdinstaller's "discussion" list about the
way they filter passwords.  Basically, the filter they placed has too many
false postives.  I've got a patch here to relax this:

http://www.labthug.com/~adrian/bsdinstaller/passwd.patch

I'm also still interested in how the installer builds, installs, and ties
together with the nrelease process, considering that the only testing I
currently know how to give the above patch is a compile.  Any information you,
or someone else, can pass along will be greatly appreciated.

Thanks again,

Adrian