Re: [Apachetoolbox-devel] General: logging revisited...

[Kevin J M. <km...@WP...>]

Best thing I can think of is to examine the Makefile and look at the
"install" target.

However, one of my projects I have on the backburner right now is to
integrate "checkinstall" into ATB.  This program claims to cure just this
problem, while also allowing the building of RPMs, debs, & Slack packages
from the source.

Dunno.  Started working on it, but it requires a number of changes (at
least at initial examination).

-- 
Kevin

On Wed, 24 Jul 2002, Toni Mueller wrote:

>
>
> Hi,
>
> while I acknowledge that mostly the respective upstream authors are
> guilty, is there an easy way to generate useful logs from the
> install script so as to get a complete list of files (target files,
> that is) that get installed?
>
> Stupid logging like "Installing F-Word/Junk.php" only underlines the
> need for heavy swearing, but doesn't solve any problem, like finding
> out where the heck some obscure library wound up :(
>
> No, constantly running "find" on the system to see these is not
> an option when precise info could be as cheap as not suppressing
> the echoing of commands in a Makefile.
>
>
> Best,
> --Toni++
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Apachetoolbox-devel mailing list
> Apa...@li...
> https://lists.sourceforge.net/lists/listinfo/apachetoolbox-devel
>