[be] [task #8307] check for runtime dependencies from ./configure to bibledit

[Teus Benschop]

Update of task #8307 (project bibledit):

                  Status:                    None => Cancelled              
             Assigned to:                    None => teus                   

    _______________________________________________________

Follow-up Comment #1:

Thinking about moving the check on run-time dependencies to the bibledit
binary itself instead of to the configure script, it sounds to me that the
following might happen in that case:

Packages will be created where the packager might overlook these
dependencies, since these are not caught by the ./configure script. People
will install the bibledit package, try to run it, then discover that it
refuses to run because it can't find certain critical runtime dependencies.

But if these dependencies are caught at configure time, that is much
earlier.

The configure script checks for libraries whether these are there, because
the libraries are run-time dependencies. Executable are just the same, and
bibledit's configure script makes no exception for one type of the other,
hence it checks for all.

All run-time dependencies should be listed in a package, so that if for
example a user removes git from his system, the package system will complain
and suggest to remove bibledit also. That way the user is warned that if he
wishes to remove git, he loses bibledit also. He can then make up his mind
what to do.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?8307>

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