On Thu, Jul 16, 2015 at 04:50:35PM +0200, Cyril Brulebois wrote: >Hi, > >If adding support for a variable looks like a good idea, how should we >name it? > >Using sources.debian.net, looking for DEBIAN_INSTALLER returns 3 hits: > - obs-build > - live-build > - libdebian-installer > >live-build actually uses longer variable names, so not an issue: >| LB_DEBIAN_INSTALLER >| LB_MIRROR_DEBIAN_INSTALLER >| LB_PARENT_DEBIAN_INSTALLER >| LB_PARENT_MIRROR_DEBIAN_INSTALLER > >obs-build uses the same variables. > >libdebian-installer uses DEBIAN_INSTALLER__* for define/#include guards, >plus a LIBDEBIAN_INSTALLER_MAP_REAL #define. > >So DEBIAN_INSTALLER shouldn't be an issue. Maybe something more specific >would make it easier to check for later…
We could use DEBIAN_INSTALLER_STEP or similar to pass on information about what the state of the installer is, even. Or maybe that's more detail than we need right now. :-) DEBIAN_INSTALLER_RUNNING=y for a sensible default to check? -- Steve McIntyre, Cambridge, UK. st...@einval.com Google-bait: http://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
