also sprach Junichi Uekawa <[EMAIL PROTECTED]> [2005.11.02.1506 +0100]: > It is quite possible that apt-pinning is working against us. > I don't think build-dep resolver really takes much consideration > about experimental. > > We could make apt-pinning work so that it will always > prefer experimental over unstable when experimental is > used.
I don't think this is the solution. I think the build dependency
resolution just has to become version-aware and use --target-release
to install the ones that cannot be satisfied without pinning.
apt-cache policy has the output you can use to make this work.
Attached is a shell script to determine the target release.
Note that pbuilder must not set --target-release for all packages,
only those that need it. That is, it could run the script for each
dependency, then group them according to target release, then run as
many apt-get commands as there are groups.
In the mean time, here's my workaround: I use the following hook as
D99shell:
#!/bin/bash
PROMPT='do you want to spawn a shell [y/N]? '
TIMEOUT=${SHELL_TIMEOUT:-30}
echo
echo
read -p"$PROMPT" -t$TIMEOUT -n1 ans < /dev/tty > /dev/tty || echo -n timeout.
echo
if [[ $ans = y ]] || [[ $ans = Y ]]; then
/bin/bash --login -i < /dev/tty &> /dev/tty
rm -f /root/.bash_history /root/.bash.prompt
fi
Then, if I know that I will need to help pbuilder with build
dependencies, I just install them in that shell with
--target-release, and exit when I am ready to hand over to pbuilder.
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer and author: http://debiansystem.info
`. `'`
`- Debian - when you have better things to do than fixing a system
depresolv.sh
Description: Bourne shell script
signature.asc
Description: Digital signature (GPG/PGP)
