Re: Bug#54985: debian-policy: handling of shared libraries
>>>>> "Roland" == Roland Rosenfeld <roland@debian.org> writes:
Roland> - If we don't have enough machines available for the above
Roland> idea, it would be nice, if someone would create packages
Roland> named slink-buildenv, potato-buildenv and so on, which
Roland> create a changeroot environment, which gets all base
Roland> packages. Then you can enter this chroot environment and
Roland> do an "apt-get build-essentials" as well as getting all
Roland> build-dependencies (is there some public available tool,
Roland> which can automate this?) and you can build slink packages
Roland> on your potato system (or vice versa). This technique
Roland> also gives the developer the chance to test his
Roland> Build-Dependencies, because in the chroot environment you
Roland> will notice, if some packages are missing...
You can already do something like this, with by extracting base2_1.tgz
or base2_2.tgz from the boot disk set, configuring it (eg create files
like /etc/resolv.conf), and installing the development packages you
require (eg with apt).
<plug>
Part of this process (ie extracting and configuring
base2_2.tgz) is done automatically by my diskless package. However,
this only currently works for potato, as the slink base2_1.tgz came
with lots of problems, eg file permissions not set correctly).
</plug>
--
Brian May <bam@debian.org>
Reply to: