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

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

This is a forwarded message
From: Toni Mueller <su...@oe...>
To: "Kevin J. Menard, Jr." <km...@WP...>
Date: Wednesday, July 24, 2002, 9:08:09 AM
Subject: General: logging revisited...

===8<==============Original message text===============

Hi Kevin,

On Wed, Jul 24, 2002 at 08:10:50AM -0400, Kevin J. Menard, Jr. wrote:
> would imagine most upstream authors spend a lot of time coding their
> software, and thus have no reason/need to uninstall it.  Another thing that

granted. As said, the thing to do - imho - is to at least just
echo the actual install commands for the record, so someone or
some program can pick the files up at a later date _again_ and
eg. create a tarball to install on a different box.

(That's what I do with ATB: Compile and test on one box, then tar
up and move to another, unpack &test again before going live. If
I don't know which files end up where, I've got a problem...).

> comes to mind is that just because the "install" target picks a path to put
> the files into, that does nothing if the user decides to modify those files
> (and save those changes) or if he moves the files to another path (of
> course, this should obviously fail).  Maybe a better way would be to make a

Well, the first thing to know is where the files go before I can
start and modify them in the first place. I was also under the
impression that it is a generally accepted systems (and package)
management principle to record which files go where at installation
time.

> checksum of the installed files and compare them before a delete.  If the
> checksums don't match, the file was modified, and shouldn't be removed.

Ok... (or: ask).

> The source tarball for this package also contains installwatch.  Last time I
> talked to Bryan about it, he wanted to keep installwatch in, so people could
> see that the ATB wasn't grabbing trojaned tarballs or something.

That's a good idea anyway, although these are different problems to
be solved: One is to make sure we don't get bogus source packages,
and one is (after compiling Apache) to generate Apache packages for
(local) distribution. installwatch seems to solve the former problem,
but the solution to the latter problem is unclear. Your first (?)
reply suggested that this checkinstall-package also contains software
to solve this latter problem and, on top of that, be able to generate
packages conforming to certain standards so that they integrate with
already-existing package management tools. I don't see the conflict,
but also didn't look at the package yet.

> http://asic-linux.com.mx/~izto/checkinstall/
> 
> Have fun :)

Well, I guess I'll do.

> TOFU?  If that means I included all of your email at the bottom for no

I didn't say "for no good reason", but otherwise that's what i meant.

> reason, it's just because I typed that from an ssh session late last night,

That's my usual operating mode for writing just about any mail, except
that I'm not always doing it late at night.

> and was just too lazy to delete the lines from pine :-P  But, if you have a
> decent mail client, it should ignore or otherwise indicate, that anything
> after the "-- <CR><LF>" is superfluous :)

Hmm... I have mutt and vim as my editor. That should be
decent enough...


Best,
--Toni++

===8<===========End of original message text===========



-- 
Best regards,
 Kevin                            mailto:km...@wp...