kas for development (Yocto)

[Jonas Gorski]

Hi,

we are trying to move from repo to kas for our Yocto based OS, which
is (mostly) working fine for CI and the "just want to build" case, but
I am struggling with using kas for development.

My development mode is often playing around with config settings,
adding/removing commits, adding local changes etc, and there its easy
to accidentally overwrite my changes when I forget to add the
appropriate arguments to kas commands.

So what I'm currently imagining is a don't-touch-by-default mode for
kas, i.e. don't touch the config unless I explicitly tell it to, and
don't touch the repos unless I explicitly tell it to. Maybe some flag
for checkout that sets up a .config.yaml that skips those after the
initial setup for build/shell.

That way it would allow me to easily do a kas shell, muck around, drop
out, kas build cycle.

Does this make sense?

Best regards,
Jonas

--
BISDN GmbH
Körnerstraße 7-10
10785 Berlin
Germany
Phone: +49 30 610 816 100
Managing Directors: Dr.-Ing. Hagen Woesner, Andreas Köpsel


Commercial
register: 
Amtsgericht Berlin-Charlottenburg HRB 141569 B
VAT ID No: 
DE283257294