Re: libsigsegv questions

[Bruno Haible]

Hi Eric,

Eric Blake wrote:
> Does libsigsegv have a bug-reporting address?  It uses the old-style
> AC_INIT, and thus './configure --help' doesn't mention where to send bug
> reports, and doesn't install any programs with --help output.  Neither
> http://www.gnu.org/software/libsigsegv/ nor
> https://savannah.gnu.org/mail/?group=libsigsegv mention any lists or
> aliases, let alone a link to mail archives.

The homepages
  http://www.gnu.org/software/libsigsegv/
  http://libsigsegv.sourceforge.net/
mention two email addresses; these email addresses occur also in the AUTHORS
file and in the ChangeLog file, so that's where most people write. Anyway,
one of the two addresses that you picked was right :-)

> Also, is there a git repository (either master or mirrored) that holds the
> source, rather than being forced to go through cvs.sv.gnu.org?

The sources available at the location mentioned in
  http://savannah.gnu.org/cvs/?group=libsigsegv
Yes, it's only CVS.

> I'm considering using libsigsegv in m4, and I'm debating about including
> libsigsegv as a subpackage rather than requiring it as an externally
> installed dependency.

I would recommend to use it only as an external dependency. The reason is that
libsigsgev sometimes sees rapid new releases due to new platforms. (A new
release for 64-bit MacOS X is pending, for example.) If you include the
library in your package, it's not so easy for the users of your package to
use the newest libsigsegv version.

Anyway, if you include GNU libsigsegv in your package, I would ask to include
the last released tarball at any moment, not the bleeding edge from the CVS
repository - because that is sometimes broken.

For your information, attached you find the libsigsegv detection macro from
GNU clisp.

Bruno

sigsegv.m4
Description: Text document