<snip>
Another option would be to build packages using another system in an alternate root and then install them on the router. The trouble with this is that as far as I can tell, emerge doesn't give the option to build a package without installing it.
ebuild <path_to_ebuild> package
Perhaps it would work to simply nfs-mount (using nosquashroot, which probably isn't a big deal if that option's only available to a single IP) the entire router's filesystem and emerge using that root from the server.
I would just maintain a chrooted copy of the firewall os, with the only difference being the presence of gcc. If testing the package before deployment is an issue, simply maintain a further copy of the firewall in a chroot, (or root), which is identical. You can then try the package, (or package and kernel), on that.
MAL
-- [EMAIL PROTECTED] mailing list
