ganglia-developers

[Ganglia-developers] "gstat" name collision

[Preston S. <ps...@ph...>]

 Everybody have a good new year?

 I've just got a bug report from Debian that both ganglia and 
 "Firebird", an Interbase-based database engine provide a binary
 located at /usr/bin/gstat.

 I figure there's a few solutions:
  1) We rename gstat to something else (gangliastat? gstatus?)
  2) We get Firebird to rename gstat 
  3) I rename gstat for purposes of Debian packages 
  4) Place gstat in Debian in a different location, (not /usr/bin)
  5) The Debian Firebird maintainer and I make ganglia and firebird
     conflict, so they both can't be installed at the same time.

 3, 4, and 5 are less than optimal solutions. Debian packages not
 behaving like non-debian ones isn't good, and it seems arbitrary to
 make a database engine and ganglia conflict for no good reason.

 Ideas?

 -Preston
   
-- 
 Preston Smith                                <ps...@ph...>
 UNIX Analyst                  Purdue University Physics Computer Network
 GPG Fingerprint:      6D27 5DAA F58D C42B 7A6B  8F48 04E4 2465 F353 03F6

Re: [Ganglia-developers] "gstat" name collision

[matt m. <ma...@cs...>]

preston-

we should rename gstat to gstatus i guess.  it would be nice to have a 
symbolic link (named gstat) which points to gstatus if firebird is not 
installed.  if firebird blasts the symbolic link... well.. no harm done.

sound ok?  any other ideas?
-- 
matt

Today, Preston Smith wrote forth saying...

>  Everybody have a good new year?
> 
>  I've just got a bug report from Debian that both ganglia and 
>  "Firebird", an Interbase-based database engine provide a binary
>  located at /usr/bin/gstat.
> 
>  I figure there's a few solutions:
>   1) We rename gstat to something else (gangliastat? gstatus?)
>   2) We get Firebird to rename gstat 
>   3) I rename gstat for purposes of Debian packages 
>   4) Place gstat in Debian in a different location, (not /usr/bin)
>   5) The Debian Firebird maintainer and I make ganglia and firebird
>      conflict, so they both can't be installed at the same time.
> 
>  3, 4, and 5 are less than optimal solutions. Debian packages not
>  behaving like non-debian ones isn't good, and it seems arbitrary to
>  make a database engine and ganglia conflict for no good reason.
> 
>  Ideas?
> 
>  -Preston
>    
>