On 31/10/12 12:42 PM, Frank Gard wrote: > Why are some of the vars named LB_* while others aren't. Bugs like this one > will happen...
I just had a look at this too. Near as I can figure, the ones named LB_ are considered options of live-build itself, whereas the other ones belong to the individual programs. They appear to be named this way because at one time they were internal (i.e. no public interface to set them was provided). That distinction looks like it's now gone, so I don't see a strong argument for leaving them without an LB_ prefix anymore, either. # Internal stuff (FIXME) APT_OPTIONS="${APT_OPTIONS}" APTITUDE_OPTIONS="${APTITUDE_OPTIONS}" DEBOOTSTRAP_OPTIONS="${DEBOOTSTRAP_OPTIONS}" CDEBOOTSTRAP_OPTIONS="${CDEBOOTSTRAP_OPTIONS}" GZIP_OPTIONS="${GZIP_OPTIONS}" ISOHYBRID_OPTIONS="${ISOHYBRID_OPTIONS}" EOF That is, the FIXME probably was an acknowledgment that the lack of a public interface was a problem (now fixed). Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org