• Status Assigned
  • Percent Complete
  • Task Type Feature Request
  • Category Core
  • Assigned To
    brent s.
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version 1.0
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: BDisk
Opened by Anonymous Submitter - 04.01.2018
Last edited by brent s. - 04.01.2018

FS#34 - Add build time support for only completeing single phase of build at a time

Add a build time option for only completing one phase of the build process at a time
For example: I would like be able to build the chroot without compiling the final .iso. I would also like to compile the final .iso from a previously build chroot without having to re-install the chroot. I would like to do this so I can work on the overlay without having to do a re-install. This would greatly speed up testing and debugging. Also, being able to install the base chroot without compiling the rest would aid in development. Just a design time decision to consider

brent s. commented on 04.01.2018 02:49

yeah, i need to figure out just how i'd *expose* that. the actual build porocess already is segmented, just need to figure out how to make it accessible from the shell

GI Jack: All American zero commented on 04.01.2018 21:23
Decent way to do it would be with --options. I see you already use argparse, which is a good start.

Each option can have its own function that calls what it needs. Its also advisable to add --clean options such as --clean-all --clean-chroot, --clean-iso for starting over.


brent s. commented on 04.01.2018 21:55

--options doesn't quite make sense; it's non-descript. it'd have to be something like --buildlevels or something, with some sort of name signifier or the like. again, rewriting so i'm not stressing ovr it yet.

GI Jack: All American zero commented on 05.01.2018 20:42

no, not litterally --options, but name invidual phase with an switch. i.e. --build-chroot and --mkinitcpio, and --build-overlay and --make-iso

brent s. commented on 05.01.2018 20:47

mmm. i'd prefer not to make explicit args, because that clutters and complicates. i'll probably implement it in a comma-separated list that gets .split()'d or via an nargs type if anything, that way i won't have to exhaust shortflags

GI Jack: All American zero commented on 07.01.2018 15:15
explicit args aren't bad with argparse. Its very good at handling them. Also, don't worry too much about shortflags. GNU is NOT UNIX.

also, I would like an option for --init-profile

that would create an blank build.ini and copy the contents of /var/lib/bdisk to either a target directory, or if none, the current directory. then set [build] basedir= in the newly created build.ini to the target directory.


Available keyboard shortcuts


Task Details

Task Editing