also sprach Carsten Aulbert <[EMAIL PROTECTED]> [2008.07.17.0835 +0200]: > (1) Is there a standard way to detect which files have been added > to the system? Right now I'm doing a full find of the whole > "system" before and after and extract the changed files.
Have a look at stow?
Also, there are checkinstall and installwatch, but be careful when
using them as they might cause data loss. From my book:
\programme{checkinstall} is limited in what it can do. To be
precise, the packages it creates can only install files, and
\programme{checkinstall} does not care where it installs them. You
can overwrite files in home directories with
\programme{checkinstall}, among other things. The generated
packages cannot modify files. If the installation routine modifies
existing files, they will be part of the generated package in
their entirety. A horror scenario occurs when an installation
routine adds a user by modification of \file{/etc/passwd}, which
is subsequently included in the package. Installation of the
package causes \file{/etc/passwd} to be completely replaced, and
the deinstallation of the package removes the file, breaking the
system in half. The generated packages also fail to register their
configuration files with \programme{dpkg}\footnote{But see
\link{http://bugs.debian.org/284786}!}, therefore paving the way
for upgrades that overwrite local configuration file changes.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
"never attribute to malice what can be
adequately explained by incompetence."
-- mark twain
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
