OooooooooooooooooooooooooooooO
  Frequently Asked Questions
OooooooooooooooooooooooooooooO


Q1: I can't use paco to log it's own installation: "error while loading shared
    libraries: /usr/lib/libpaco-log.so: cannot open shared object file: No such
    file or directory"

R1: As of paco-1.10.4 it is possible to log the own paco's installation: Just
    type "make logme" after "make install".


Q2: When building LFS, paco does not properly log the installation of glibc
    in chapter 6 (some files are not logged)

R2: This is because in the chapter 6 some of glibc files are installed
	using statically linked sln. To have a proper glibc log you can run the
	following in chroot after installing glibc:

		find /lib -type l | while read name
		do
			if [ "$(paco -f glibc | grep "$(readlink $name)")" != "" ]
			then
				echo $name
			fi
		done | paco -lp+ glibc-<GLIBC_VERSION>

	Or the following simpler command, if you run it right after installing
	glibc, and before installing any other package:
        
		find /lib | paco -lp+ glibc-<GLIBC_VERSION>


Q3: Why doesn't paco log directories?

R3: When a directory is created, using either mkdir or install, all the partial
    directories in its path need to be created too. Even if they already exist,
    the system call mkdir() may be called for every partial directory in the
    path. Thus, for example:

        $ paco -l 'install -d /usr/share/man/man1'

    would log the following directories:

        /usr
        /usr/share
        /usr/share/man
        /usr/share/man/man1

    And I think this would be a bad thing: All logs would be bloated with many
    directories, and the list of files could be too large. Also, most of the
    directories will be shared among many packages, resulting in a big mess...


Q4: Is it safe to launch paco with sudo?

R4: Yes. Here you can see a thread in the paco mailing list that discusses this
    issue:

	http://sourceforge.net/mailarchive/message.php?msg_name=op.s0crq8an4bwnuy%40slack.homenet


Q5: Is it safe to launch sudo with paco?

R5: No. For example the command:

        paco -lp foobar-1.0 "sudo make install"

    would not produce any error message, and the package would be actually
    installed, but paco would not be able to monitor the installation and no
    files would be logged.
    This is due to LD_PRELOAD limitations on suid programs like sudo.


Q6: How can I stay informed about new releases of paco?

R6: The best way is to subscribe to new releases in the paco project page at
    freshmeat.net (http://freshmeat.net/projects/paco/).
    You have to be a freshmeat registered user to be allowed to do so.