On 21/08/15 15:42, Thomas Schmitt wrote: > Well, i need to make some progress with uploading. > So i'll go on with the VM for now. I need to learn a bit more > about what sbuild does. On the long run it looks cleaner.
Hi Thomas, sbuild basically implements what you have started to build in your VM. The main advantage of it is the "...and throw everything away to get a clean starting point", so you have a reproducible and minimal build environment. Also sbuild's basic set of packages does not include an X server. However, you now have a VM containing debian's equivalent of a "latest of all open source stuff" machine. It can be fun to play around on it, and if you find any bugs in those (not-yet-in-stable) versions, I'm sure the maintainers will greatly appreciate reports. (Just don't depend on "sid" in the same way as you would on a "stable". Have backups.) > > Which one to install ? > dput: /usr/bin/dput > dput-ng: /usr/bin/dput > My Jessie obviously has "dput" installed. I have "non-ng" dput aswell, havn't tried the new one yet. > > So many branches ... > Just to add to the branches: The same thing sbuild does (build in cleanroom chroot to verify build-depends) is also implemented as "pbuilder". As an alternative to dput{,-ng}, there is also dupload. I wouldn't say there's a definitive better one, but having more than one tool for the same problem might turn in handy if one has a bug and/or breaks. I ultimately chose sbuild over pbuilder because its what official buildds use. Take a look at "man devscripts" (package name also devscripts) as an overview of even more little helpers. - Danny