Should we install gcore.sh (and a gcore.1 man page)?

The offered contribution, by Nicolas Bonifas, of a man page
for the gcore shell script has raised a question vis a vis 
gdb's install script.

We have this shell script in our source tree, which invokes
gdb and makes it run the "gcore" command on a
specified process.
This was, I believe, to mimic a 'gcore' command utility
from
Sun (or some such).

But we've never installed the gcore shell script.

Should we?  Should we go ahead and put it into
$<install>/bin?
In which case we might want to accept the contributed man
page
and install that as well?

Apparently Debian's package installer does this, renaming
the
script to just "gcore" in the process.

Michael

> Should we?  Should we go ahead and put it into
$<install>/bin?
> In which case we might want to accept the contributed
man page
> and install that as well?

I think it's a useful script to install. My only concern is
that
not all configurations support the gcore command...

-- 
Joel

On Wed, 2007-10-24 at 15:10 -0700, Joel Brobecker wrote:
> > Should we?  Should we go ahead and put it into
$<install>/bin?
> > In which case we might want to accept the
contributed man page
> > and install that as well?
> 
> I think it's a useful script to install. My only
concern is that
> not all configurations support the gcore command...

Configure?

> > I think it's a useful script to install. My only
concern is that
> > not all configurations support the gcore
command...
> 
> Configure?

Or maybe check the contents of DEPFILES? If it contains
gcore.o,
then install the script, otherwise we don't.

-- 
Joel

On Wed, 2007-10-24 at 15:24 -0700, Joel Brobecker wrote:
> > > I think it's a useful script to install. My
only concern is that
> > > not all configurations support the gcore
command...
> > 
> > Configure?
> 
> Or maybe check the contents of DEPFILES? If it contains
gcore.o,
> then install the script, otherwise we don't.

That sounds good.  Then we would not have to change much
except for like Makefile.in and configure.in.  Script
something
like 'cat <host makefile fragment> | grep
"gcore.o"'

> That sounds good.  Then we would not have to change
much
> except for like Makefile.in and configure.in.  Script
something
> like 'cat <host makefile fragment> | grep
"gcore.o"'

I think you can simplify this even further by only changing
Makefile.in.
Instead of grep'ing the makefile fragment, which can only be
done in
the configure script (and is also a little error prone), I
think you
can just grep the value of $ for gcore.o.

-- 
Joel

Hello,
Any progress on this question?
Regards,
Nicolas