-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Jun 14, 2018 at 08:35:29AM -0700, Don Armstrong wrote: > On Thu, 14 Jun 2018, to...@tuxteam.de wrote: > > Took out mk-sbuild for a whirl. What I didn't like at all: when you > > invoke a command and it goes out and starts installing packages for > > you (and doing other assorted sysadmin tasks). > > You can do everything that mk-sbuild does for you manually, but when > you're setting up many different sbuild chroots, it makes things much > easier. [And it makes my response much simpler.]
Yes, I understand *why* it is doing it. It just doesn't rhyme very well with the way I do things. Pulling in dependencies at install is something I expect (and can easily check in advance, thanks to the well thought-out Debian packaging system). Calling "apt-get install" (to my *main* system, not to the chroot!) from a seemingly unrelated command is something I... dislike (there were other things I disliked, too). So this was just a heads-up for others like me. I had a look into the mk-sbuild script and decided to purge ubuntu-dev-tools. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlsjVrkACgkQBcgs9XrR2kb7JgCfdcywY9A1ZaK4rwP3gw11OBc0 qcYAniTwFq3KnAFdSRIijkZNSY+Dpk82 =bq/r -----END PGP SIGNATURE-----
