[Gnash-commit] [patch #7554] Autoinstalling gnash dependencies

[Jonas 'Sortie' Termansen]

Follow-up Comment #4, patch #7554 (project gnash):

I am quite unsure how exactly you expect from this system to work.

If I wrote a separate static script it would need to do a lot of
configure-like things such as scanning the system, figuring out which backends
to use, detecting package system and what not. In any case, it wouldn't be
static at all, and would duplicate a lot of what configure already does. :)

It'd be simpler if we could pass --install-dependencies to configure, but
that'd require running configure as root, which is simply bad manners - root
would own all the generated files.

I favor the dynamic approach, where configure tailors a list of packages
needed for the build. Ideally, the user would pass the arguments to configure,
get a list of dependencies, call my script, and then run configure
successfully.

A side note, currently it may take 1 or 2 attempts of running the script to
install everything. This is caused by unrelated bugs in configure (mainly it
may not suggest some dependencies, if others are missing. These bugs are
trivial to fix). :)

If we decide on the dynamic approach, then my current patch would work very
well -- it needs to be polished and rewritten using more M4 macros (such that
it generates the install libfoo-dev suggestions too). I'd gladly rewrite the
current patch to merge the systems.

If I rewrote the patch such that it generates the suggestions as well, would
it be acceptable into master? I don't see any graceful way to create a static
separate script that does the task, without re-inventing configure.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?7554>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/