Scott Ullrich wrote:
On Wed, Jun 25, 2008 at 12:07 PM, Scott Ullrich <[EMAIL PROTECTED]> wrote:
[snip]
I've long ago stopped trying to build from source, because the build
environment is too absurd (i.e. doing a "rm -Rf /home/pfsense/pfsense"
before every build is enough to prohibit maintaining local modifications in
a manageable way).
I am all ears to improvements. Since I am the only person that
bothers to put any time into the builder system I take offense to your
statement. I don't see how a system that builds every piece of
pfSense and packages into multiple targets (iso, embedded, etc) can be
easy.
Have you by chance take a look at the FreeBSD builder system?
Please accept my apologies for being too harsh in my comment. It was not
my intention to be offensive.
Yes, I know that FreeBSD's /usr/src/release/Makefile is a nightmare, but
still it has hooks for tolerating some amount of local modifications
(i.e EXTSRCDIR, EXTPORTSDIR).
Back to pfsense, why use /home/pfsense/pfsense as a working (scratch)
dir? I've been thinking for some months, instead of cleaning the source
dir and then checking it out from scratch the next time, about copying
the files to the staging area and always leave the source tree alone.
Every couple of months I try working my mind around the pfPorts
peculiarities, but I must say that I always get pissed about the huge
variability of the shell scripts used in builder system, and the 'all
from scratch' attitude of the builder system itself. I've already lost
some set of patches twice because I forgot to save it before building.
I hope the migration to git goes well, I promise I'll try to help you if
I can save my work locally and not redo it every time from scratch.
And, by the way, thanks a lot for keeping your commitment to the project
so high.
Angelo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
