Re: [gentoo-user] emerge --resume question
Peter Campion-Bye wrote: Hi, Trying to do an 'emerge -e world' I come up against the odd package that doesn't build without some intervention. I know I can do 'emerge --resume --skipfirst' and carry on, but sometimes the broken package could be built ok with a little intervention, for example, my build breaks on pilot-link, which can be simply fixed with 'FEATURES=-sandbox emerge pilot-link'. Problem is, I can't do a resume after this as the emerge list from the world build has been blatted when I emerged pilot-link. So, is there any way I can preserve the state of the world build, so that after building the breaking package I can do a --resume --skipfirst and carry on with the world build? Any other suggestions for workarounds? thanks I did this once. I renamed the emerge.log then did what needed doing and then put the back-up back to it's original name, erasing the little that was generated while fixing something. It may not work in every case though but it may be worth a try. Dale :-) :-) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge --resume question
On Monday 03 April 2006 20:39, Peter Ruskin wrote: On Monday 03 April 2006 12:06, Peter Campion-Bye wrote: Hi, Trying to do an 'emerge -e world' I come up against the odd package that doesn't build without some intervention. I know I can do 'emerge --resume --skipfirst' and carry on, but sometimes the broken package could be built ok with a little intervention, for example, my build breaks on pilot-link, which can be simply fixed with 'FEATURES=-sandbox emerge pilot-link'. Problem is, I can't do a resume after this as the emerge list from the world build has been blatted when I emerged pilot-link. So, is there any way I can preserve the state of the world build, so that after building the breaking package I can do a --resume --skipfirst and carry on with the world build? Any other suggestions for workarounds? I'm just experiencing the same thing - with over 800 ebuilds this is an important question. I'm noting the problem ebuilds in a log file manually, so I can see to them when it's all over. This is resilient to the single merge between resumes case in 2.1_pre. For 2.0, you can manually back up and restore /var/cache/edp/mtimedb. -- Jason Stubbs -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge --resume question
On Monday 03 April 2006 22:12, Peter Ruskin wrote: On Monday 03 April 2006 13:12, Jason Stubbs wrote: I'm just experiencing the same thing - with over 800 ebuilds this is an important question. I'm noting the problem ebuilds in a log file manually, so I can see to them when it's all over. This is resilient to the single merge between resumes case in 2.1_pre. For 2.0, you can manually back up and restore /var/cache/edp/mtimedb. Sorry Jason, I don't understand. How would I backup and restore /var/cache/edp/mtimedb and what would that do? It does as the opening poster asked: So, is there any way I can preserve the state of the world build, so that after building the breaking package I can do a --resume --skipfirst and carry on with the world build? The not very aptly named mtimedb file contains the resume list among other things. Hence, copying it somewhere else before fixing a broken build and copying it back after will preserve the resume list. Don't do it for more than single ebuild maintenance though as the file contains other things too. -- Jason Stubbs -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge --resume question
This is resilient to the single merge between resumes case in 2.1_pre. For 2.0, you can manually back up and restore /var/cache/edp/mtimedb. -- Jason Stubbs Thanks Jason, I'll give that a try. Regarding the original problem with pilot-link, there is AFAIK no way to specify FEATURES on an individual package basis (ie put 'app-pda/pilot-link -sandbox' into a file named package.features, in the style of the package.use file) - is that correct? Thanks -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge --resume question
On Mon, 3 Apr 2006 16:45:39 +0100 (BST), Peter Campion-Bye wrote:
Regarding the original problem with pilot-link, there is AFAIK no way to
specify FEATURES on an individual package basis (ie put
'app-pda/pilot-link -sandbox' into a file named package.features, in
the style of the package.use file) - is that correct?
You can use /etc/portage/bashrc to set anything on a per-package basis.
Put this in /etc/portage/bashrc
for MY_ENV in ${PN} ${P} ${PF}; do
if [ -f /etc/portage/env.d/${CATEGORY}/${MY_ENV} ]; then
source /etc/portage/env.d/${CATEGORY}/${MY_ENV}
fi
done
And put 'FEATURES=-sandbox in /etc/portage/env.d/app-pda/pilot-link
--
Neil Bothwick
I understand the answers, the questions throw me.
signature.asc
Description: PGP signature
Re: [gentoo-user] emerge --resume question
Regarding the original problem with pilot-link, there is AFAIK no way to
specify FEATURES on an individual package basis (ie put
'app-pda/pilot-link -sandbox' into a file named package.features, in
the style of the package.use file) - is that correct?
You can use /etc/portage/bashrc to set anything on a per-package basis.
Put this in /etc/portage/bashrc
for MY_ENV in ${PN} ${P} ${PF}; do
if [ -f /etc/portage/env.d/${CATEGORY}/${MY_ENV} ]; then
source /etc/portage/env.d/${CATEGORY}/${MY_ENV}
fi
done
And put 'FEATURES=-sandbox in /etc/portage/env.d/app-pda/pilot-link
Very neat solution Neil, thanks.
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge --resume question
On Monday 03 April 2006 16:45, Peter Campion-Bye wrote: Regarding the original problem with pilot-link, there is AFAIK no way to specify FEATURES on an individual package basis (ie put 'app-pda/pilot-link -sandbox' into a file named package.features, in the style of the package.use file) - is that correct? You can do this from the command line: FEATURES=-sandbox emerge app-pda/pilot-link Thanks, I know that, the question was how to arrange for specific features to apply only to an individual package in the middle of an 'emerge -e world'. It would be nice if the package.use functionality could be mirrored with a package.features file, but I suppose it's needed so rarely that it's not worth the effort on the part of the portage devs. -- gentoo-user@gentoo.org mailing list
