[gentoo-portage-dev] emerge interruption - is it/will it be possible?

[gentoo-portage-dev] emerge interruption - is it/will it be possible?

[Pavel Vondricka]

Hi,
I often would like to continue with a partly done emerge (e.g. manually 
interrupted compilation or compile failure -because of some stupid USE flag 
setting, aso.), without emerge starting from the scratch again. 
It is not only "a bad dream at the end of a 12-hour compilation", but I'd also 
like to just unpack the sources, stop emerge, edit/patch the sources 
manually, and then let emerge continue and compile and install it, sometimes.

Is it possible with the current emerge or will it be possible with the future 
portage-ng?
What is the meaning of emerge -resume? It never did anything for me.

Thanks,
Pavel

-- 
###########################################################################
# mailto:Pavel.Vondricka@ff.cuni.cz
# ICQ:143159880
# Jabber:wanthalf@jabber.cz
# http://web.ff.cuni.cz/~vondric
#
# Muzete mi psat cesky s libovolnym kodovanim (UTF-8, ISO-8859-2,
# windows-1250, atd. ...)
###########################################################################


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] emerge interruption - is it/will it be possible?

[Daniel Robbins]

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

On Thu, 2003-12-04 at 07:21, Pavel Vondricka wrote:
> Hi,
> I often would like to continue with a partly done emerge (e.g. manually 
> interrupted compilation or compile failure -because of some stupid USE flag 
> setting, aso.), without emerge starting from the scratch again. 
> It is not only "a bad dream at the end of a 12-hour compilation", but I'd also 
> like to just unpack the sources, stop emerge, edit/patch the sources 
> manually, and then let emerge continue and compile and install it, sometimes.

> Is it possible with the current emerge or will it be possible with the future 
> portage-ng?

One easy way to get functionality like this is to "emerge ccache". Then
restarting merges should used previously-cached compiles and make things
go a lot faster.

> What is the meaning of emerge -resume? It never did anything for me.

I honestly don't know. It was something added to the code after I handed
over development to carpaski.

Regards,

Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-portage-dev] emerge interruption - is it/will it be possible?

[Pavel Vondricka]

Anyway, it would be nice if portage could do these things separately on 
demand:
1) unpack (and patch?) the sources only
2) run ./configure on the unpacked sources only
3) run make on the unpacked sources only
4) install only

Is it possible to add it to some portage-ng wishlist, or is it just non-sense/
impossible?

Pavel

-- 
###########################################################################
# mailto:Pavel.Vondricka@ff.cuni.cz
# ICQ:143159880
# Jabber:wanthalf@jabber.cz
# http://web.ff.cuni.cz/~vondric
#
# Muzete mi psat cesky s libovolnym kodovanim (UTF-8, ISO-8859-2,
# windows-1250, atd. ...)
###########################################################################


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] emerge interruption - is it/will it be possible?

[Thomas de Grenier de Latour]

On Fri, 5 Dec 2003 13:56:13 +0100
Pavel Vondricka <Pavel.Vondricka@ff.cuni.cz> wrote:

> Anyway, it would be nice if portage could do these things separately
> on demand:
> 1) unpack (and patch?) the sources only
> 2) run ./configure on the unpacked sources only
> 3) run make on the unpacked sources only
> 4) install only
> 

This are (among a few other ones) the tasks "ebuild" knows. Configure
and make are in the same task though. I often use "ebuild
/path/to/ebuild compile install qmerge" to resume an aborted emerge
after some patching or things like that, it works well in general.

Have a look here for the list of available commands:
http://www.gentoo.org/doc/en/gentoo-howto.xml#doc_chap4

-- 
TGL.

--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] emerge interruption - is it/will it be possible?

[Pavel Vondricka]

Oh, I'm sorry I haven't found it! And thank you very much!
Pavel

> On Fri, 5 Dec 2003 13:56:13 +0100
>
> Pavel Vondricka <Pavel.Vondricka@ff.cuni.cz> wrote:
> > Anyway, it would be nice if portage could do these things separately
> > on demand:
> > 1) unpack (and patch?) the sources only
> > 2) run ./configure on the unpacked sources only
> > 3) run make on the unpacked sources only
> > 4) install only
>
> This are (among a few other ones) the tasks "ebuild" knows. Configure
> and make are in the same task though. I often use "ebuild
> /path/to/ebuild compile install qmerge" to resume an aborted emerge
> after some patching or things like that, it works well in general.
>
> Have a look here for the list of available commands:
> http://www.gentoo.org/doc/en/gentoo-howto.xml#doc_chap4

-- 
###########################################################################
# mailto:Pavel.Vondricka@ff.cuni.cz
# ICQ:143159880
# Jabber:wanthalf@jabber.cz
# http://web.ff.cuni.cz/~vondric
#
# Muzete mi psat cesky s libovolnym kodovanim (UTF-8, ISO-8859-2,
# windows-1250, atd. ...)
###########################################################################


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] emerge interruption - is it/will it be possible?

[R. C. James Harlow]

Pavel Vondricka wrote:

This seems to be two front-end issues that are actually pretty different.

> Hi,
> I often would like to continue with a partly done emerge (e.g. manually 
> interrupted compilation or compile failure -because of some stupid USE flag 
> setting, aso.), without emerge starting from the scratch again. 

The first is that you want an emerge to be a "transaction", and if it's 
interrupted you want to be able to resume the transction where you left 
off (particularly if you haven't done a different emerge immediately 
before).

> It is not only "a bad dream at the end of a 12-hour compilation", but I'd also 
> like to just unpack the sources, stop emerge, edit/patch the sources 
> manually, and then let emerge continue and compile and install it, sometimes.

And this is the second issue, that you'd be happy with something like 
PORTAGE_BREAKPOINT="kde-base/kdebase-3.2:compile", and the front-end 
sending itself a SIGSTOP just before that stage, so you could patch kde 
and then `fg` to resume it.

> Is it possible with the current emerge or will it be possible with the future 
> portage-ng?

They're both possible now, but it would be interesting to have emerge be 
a bit cleverer about it (afaik neither of these operations are possible 
with emerge, only with ebuild).

Let me know if I've got the wrong end of the stick.

--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] emerge interruption - is it/will it be possible?

[Paul de Vrieze]

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

On Sunday 25 January 2004 23:32, R. C. James Harlow wrote:
>
> They're both possible now, but it would be interesting to have emerge be
> a bit cleverer about it (afaik neither of these operations are possible
> with emerge, only with ebuild).
>
> Let me know if I've got the wrong end of the stick.

emerge --resume partially supports resuming a failed operation. I don't know 
though whether that means that you can just resume at the compile stage.

Besides that, I find a personal overlay tree to be the best way to go about 
peronal "fixes" to ebuilds.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]