[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: requires for lcov



Roland McGrath píše v Pá 24. 02. 2006 v 01:28 -0800:
> > If lcov calls /usr/bin/gcov, esp. if it contains a hard-coded reference
> > to this file, is absolutely perfect.
> > 
> > If lconv calls "gcov" on $PATH, then there'd be some room for
> > argumentation.
> 
> In fact it runs "gcov" using the path.  What to run can be set in a
> configuration file.  Should I make the default /usr/bin/gcov instead?  That
> would annoy someone who installed their own gcc build, but they could edit
> the config file.  I'm inclined to leave it as it is, and wish for an rpm
> pseudo-dependency meaning "there is a foobar command in the local standard
> path for users".
> 

I would make it specified in the config file to be consistent with the
spec file and add a note for the experienced users to point it to the
gcov from their gcc instalation. Something like "change this for
non-Fedora GCC instalations".

--- lcovrc.orig	2006-02-24 18:12:01.000000000 +0100
+++ lcovrc	2006-02-24 18:12:35.000000000 +0100
@@ -51,7 +51,8 @@
 genhtml_highlight = 0
 
 # Location of the gcov tool (used by geninfo)
-#geninfo_gcov_tool = gcov
+# Change this for non-Fedora GCC instalations
+geninfo_gcov_tool = /usr/bin/gcov
 
 # Adjust test names to include operating system information if non-zero
 #geninfo_adjust_testname = 0


> My thinking in using the file dependency was as mentioned, that gcov might
> conceivably move to a different package in the future.  (There is no
> special reason to expect that to happen.)

That is reasonable.


		Dan



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]