Restructuring questions
I have a few questions I'd like to put out to you all (perhaps Daniel in
particular) in relation to some restructuring work I'm doing on the
live-build codebase (a contribution for which I know I haven't yet
provided much detail on what exactly I'm changing, but I will do soon,
and will obviously be subject to Daniel's approval if its to be adopted).
So the questions:
1) What exactly is the use case for a user running live-build with a
copy of the utility's code within their build directory? Does anyone
actually do this rather than running an installed copy? If so why? I
don't know why the codebase bothers to offer such support.
I can see in binary_syslinux that the local config may provide the
bootloader as an alternative to the /usr/share copy through this
directory structure, but that can be supported without this. Similarly
with the bin/Packages script file.
2) The point of the local/bin directory of your build directory is what?
It's created by the config script, and then used in constructing a PATH
variable in the common.sh functions script
(PATH=${PWD}/local/bin/:{$PATH}), but the only place I see the PATH
variable is used is in the chroot.sh functions script, which seems to
ignore this since it's being set to a hard coded value when used there.
A version 3.x changelog entry describes it as "for executables
overriding not just lb scripts, but any command during live-build runs".
So is this actually needed? Is the described functionality really
actually needed pretending this actually did what it's supposed to
allow? Or is it just dead code awaiting removal, like the
source_debian-live script (which seems to have been left over from a
renaming to the source_live script)?
3) File locations. Why is /usr/lib/live/build.sh located there and not
in the build directory, and while I can perhaps understand copies of
bootloaders being in /usr/share/live/build, what about most of the rest
such as functions, why are these here under share instead of lib?
Reply to: