Re: Nicer way to manage installed build dependencies?
Dear Roger, Roger Leigh wrote: > If you build things on a regular basis, install "schroot" and "sbuild", > and configure schroot to use "snapshot" chroots. This will give you > the same setup used on the buildds. You can create snapshots from > .tar.gz|bz2|xz (file), LVM LVs (lvm-snapshot) or Btrfs subvolumes > (btrfs-snapshot), or use writable overlays (aufs/unionfs). This gives > you speed (the snapshots can be deleted almost instantaneously), and > safety (everything is built in a pristine clean temporary chroot > environment). Thanks for the suggestion, though such a setup is probably a little bit too heavy given my rather casual building and the constrained environment of my notebook. I will definitely look into it again should I ever manage to sensibly contribute to FOSS. Best regards & thank you very much for your work on Debian, Claudius -- Please don’t CC me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130318190740.4fb37...@ares.home.chubig.net
Re: Nicer way to manage installed build dependencies?
On Sun, Mar 17, 2013 at 03:03:51PM +, Claudius Hubig wrote: > due to a long-standing annoyance in freeciv-client-gtk[0], I wanted > to rebuild this package locally and noticed that there still seems to > be no way to nicely manage what > > # apt-get build-dep freeciv-client-gtk > > pulls in - it just installs the required packages and then leaves me > with them. This is obviously fine if I use a fresh chroot for every > new build, but is there really no way to either > > a) mark such packages as installed automatically in some way that >doesn’t instantly remove them again > or > b) remove all build dependencies of a given package that are not >required by others? > > I know of deborphan etc., but they are usually rather cumbersome to > use (you have to iterate manually etc.). > > Are there any obvious other ways to solve this problem? I managed to > put together a small shell script[1] that creates a dummy/meta > package, but I’d really prefer something ‘official’. If you build things on a regular basis, install "schroot" and "sbuild", and configure schroot to use "snapshot" chroots. This will give you the same setup used on the buildds. You can create snapshots from .tar.gz|bz2|xz (file), LVM LVs (lvm-snapshot) or Btrfs subvolumes (btrfs-snapshot), or use writable overlays (aufs/unionfs). This gives you speed (the snapshots can be deleted almost instantaneously), and safety (everything is built in a pristine clean temporary chroot environment). Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130318125822.gu23...@codelibre.net
Re: Nicer way to manage installed build dependencies?
Dear Florian, Florian Ernst wrote: > There is mk-build-deps in the package devscripts, and there once was > sourcedeps.debian.net (now dysfunctional) which allowed to have a > sources.list for Build-Depends-metapackages created using mk-build-deps. > I don't know when and why the latter service was discontinued, so that > doesn't help much for now, though ... Ah, mk-build-deps is actually exactly what I wanted. $ mk-build-deps -A pidgin creates a small package depending on the Build-Depends of pidgin. This also works without sourcedeps.debian.net, so it is still fully functional. Thank you very much! Best, Claudius -- Please don’t CC me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130318085601.43437...@ares.home.chubig.net
Re: Nicer way to manage installed build dependencies?
Hello all, On Sun, Mar 17, 2013 at 03:03:51PM +, Claudius Hubig wrote: > [...] > Are there any obvious other ways to solve this problem? I managed to > put together a small shell script[1] that creates a dummy/meta > package, but I’d really prefer something ‘official’. There is mk-build-deps in the package devscripts, and there once was sourcedeps.debian.net (now dysfunctional) which allowed to have a sources.list for Build-Depends-metapackages created using mk-build-deps. I don't know when and why the latter service was discontinued, so that doesn't help much for now, though ... Cheers, Flo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130318083706.gc17...@fernst.no-ip.org
