On Wed, Apr 30, 2008 at 08:21:30AM -0600, Myles Watson wrote:
I agree with the TODO of building fcode-utils as a dependency. You
could do
the check and include it if fcode-utils is not already installed.
Otherwise
the user might not know where to get it.
I'm a bit uncertain here, we also don't install ruby or perl or subversion or git or wget for the user. Yes, fcode-utils is not as common as all the other utilities but there _are_ packages (e.g. in Debian) for it, or it can be installed manually from
http://openbios.org/FCODE_suite
I'll also document that in the wiki soon. Maybe it's a good idea to install them locally in the buildrom build dir if unavailable, but where do we draw the line in general? Are there some guidelines on what we install and we expect the user to have installed already (or manually install it on demand)?
Good question. I personally would say that things that every distribution has we expect the user to install, and things that are rarer we install. Another way to do it would be to put installation instructions (at least the URL) in the warning.
Myles