David Rosal wrote:
Hello.

Just a comment on the jhalfs-1.0 paco patch.

In common/config, the PACO_EXCLUDE variable is set thusly:

    PACO_EXCLUDE=/${SCRIPT_ROOT}

I guess ${SCRIPT_ROOT} is the directory from which jhalfs is run.

Yes. It's taken directly from the config files, and expands to $BUILDDIR/$SCRIPT_ROOT.


I think directories /dev, /proc, /sys and /tmp should be also excluded by default. I suggest:

    PACO_EXCLUDE=${SCRIPT_ROOT}:/dev:/proc:/sys:/tmp

Otherwise the resulting logs will contain many unwanted files.

I did exclude the mentioned dirs in the earlier versions of the patch. In later testing it seemed it wasn't necessary, as my logs don't contain any entries from those dirs, and hence I removed them from the setting to make it look cleaner. If anyone got problems with mess in the logs, please tell me and I'll exclude the needed dirs again.


Another question:

I have tried to build LFS-6.2-pre2 with jhalfs-1.0, and I had to copy the paco tarball into the ${LFS_MOUNT_POINT}/jhalfs/sources manually, because jhalfs did not copy it automatically. This caused the build process to fail at the beggining of chapter 6.

Yes, very annoying I must admit :(
It's described in the README.PACO that the source package needs to be downloaded and copied to the sources dir manually, as the jhalfs script don't handle that part. I keep forgetting and the build bails. Luckily, you can just copy the package to the sources dir and type make again, and the build continues where it left off.

Hopefully I'll be able to incorporate automatic download when I get some free time for my computer.. ;)


Tor Olav
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to