Feature added by: Duncan Mac-Vicar (dmacvicar) Feature #312760, revision 1 Title: osc: Decouple chroot creation with package building Buildservice: New Priority Requester: Desirable Requested by: Duncan Mac-Vicar (dmacvicar) Partner organization: openSUSE.org Description: I normally need for development to build a package from source code (not using spec files). To do ths on older distros I need to create a chroot which I do now having tons of scripts which contain duplicated information that I have to maintain. Example: create-chroot-zypp-sle-10-sp4.sh Calls zypper addrepo with SDK, SP4, and then install the libzypp buildrequires, which are copy pasted from the spec file. The build service already knows what it needs to build the environment for libzypp on SP4 if knowing the base project and the package name, however this is used on build, and there is no way to tell him: build the chroot and stop. If I could say osc buildchroot SUSE:SLE-11-SP1 libzypp $targetdir I could use osc in conjuntion with schroot to quickly create the build environment without needing to maintain fake spec files or create zypper scripts. Use Case: John Doe needs to fix a bug in zypper for Factory. He is not running Factory. He does osc buildchroot openSUSE:Factory zypper /tmp/chroot He checkouts the code into /tmp/chroot and then chroot inside and builds from source. He fixes the bug using his favorite editor from outside the chroot. He did not need to create fake-spec files or create scripts with hardcoded build-requires and repositories to achieve this. Business case (Partner benefit): openSUSE.org: As a developer, it would improve my productivity when backporting or fixing old products/Factory bugs by 42%. -- openSUSE Feature: https://features.opensuse.org/312760