From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FJ7dw-0001aR-Mb for garchives@archives.gentoo.org; Tue, 14 Mar 2006 11:24:49 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5.20060308/8.13.5) with SMTP id k2EBO5pQ015972; Tue, 14 Mar 2006 11:24:05 GMT Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.204]) by robin.gentoo.org (8.13.5.20060308/8.13.5) with ESMTP id k2EBO4dE014872 for ; Tue, 14 Mar 2006 11:24:04 GMT Received: by nproxy.gmail.com with SMTP id l37so1077658nfc for ; Tue, 14 Mar 2006 03:24:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qbqglbGUv3JqfbV8/qaVPCU8jWBl61ipREU1gh8Vnvsa4hCgWyrO2P3MB5JirfluUIcM7FArIIBAs2hYV7X+fAt3FUcMrJ6OmI3670GJF73S03GlEpdy9Gv2IitGAZYPE0TWVPPf7zINSVaKAKZwtcuXDfKqX2xXjxt38WW6eSo= Received: by 10.48.239.5 with SMTP id m5mr1371198nfh; Tue, 14 Mar 2006 03:24:04 -0800 (PST) Received: by 10.49.29.4 with HTTP; Tue, 14 Mar 2006 03:24:04 -0800 (PST) Message-ID: Date: Tue, 14 Mar 2006 13:24:04 +0200 From: tvali To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] Few things, which imho would make portage better In-Reply-To: <4416A4C1.6090903@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15379_30612355.1142335444123" References: <4416A4C1.6090903@gentoo.org> X-Archives-Salt: 4281bc44-392c-46fe-8779-ba5d0f61546f X-Archives-Hash: 3c5616b28ccb4a42b631200c7eb96965 ------=_Part_15379_30612355.1142335444123 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 2006/3/14, Simon Stelling : > > tvali wrote: > > * Add package to "world" checking all dependencies, but not emerging > > * Remove package from "world" without unmerging > > Uhm, why would you want that? > On my computer, building takes several hours on some packages. I have used it in such way that it builds in several windows on the same time, but i guess that that's not at all the best practice, especially with some combinations of packages. So i would like to add all packages, seeing all blocks and inter dependencies, then start building when ready (and go out o= f home, when it builds, and be sure that it will do it's best when i'm away). > * Save all important messages into file instead of beeping (i may be away > > from home); optionally replay them at end of update > > elog can do this. Will check out. > * When updating or installing new package, if something goes wrong, still > > emerge other packages, which havent failed packages as dependencies -- > in my > > case, for example, when i do --update, for example, then the fact that > > update of first package fails does not definitely mean that i dont want > to > > update others > > --resume I know --resume, but that's not what i meant. Imagine the situation: emerge -p package1 package2 part1 (needed by package1) part2 (needed by part3) part3 (needed by package2) part4 (needed by package2) part5 (needed by both package1 and package2) package1 package2 now i start "emerge package1 package2" and go to work (or sleep or party or sauna). part2 fails -- some bug or misconfiguration. currently it means that when i came back home, i see that part1 is built, but nothing more and 4-5 hours are actually just wasted. There should be a way to have all those built when i came home: part1 (needed by package1) part4 (needed by package2) part5 (needed by both package1 and package2) package1 There should be an error message listing all others. Also, i would add them to world and then emerge so that --update would try to emerge them again, asking me about all previously failed packages when i start it, if i want t= o retry this time (yes, no, all, none). -- > Kind Regards, > > Simon Stelling > Gentoo/AMD64 Developer > -- > gentoo-portage-dev@gentoo.org mailing list > > -- tvali (e-mail: "qtvali@gmail.com"; msn: "qtvali@gmail.com"; icq: "317-492-912") =DChe eesti internetifirma lehel kohtasin tsitaati: If you don't do it excellently, dont do it at all. Because if it's not excellent, it won't be profitable or fun, and if you're not in business for fun or profit, what the hell are you doing here? Robert Townsend ------=_Part_15379_30612355.1142335444123 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 2006/3/14, Simon Stelling <blubb@gen= too.org>:
tvali wrote:
> * Add package to "world" checking all depend= encies, but not emerging
> * Remove package from "world" wi= thout unmerging

Uhm, why would you want that?

On my computer, building takes several hours on some packages. I have used it in such way that it builds in several windows on the same time, but i guess that that's not at all the best practice, especially with some combinations of packages. So i would like to add all packages, seeing all blocks and inter dependencies, then start building when ready (and go out of home, when it builds, and be sure that it will do it's best when i'm away).

> * Save= all important messages into file instead of beeping (i may be away
>= from home); optionally replay them at end of update

elog can do this.

Will check out.

> * When= updating or installing new package, if something goes wrong, still
>= emerge other packages, which havent failed packages as dependencies -- in = my
> case, for example, when i do --update, for example, then the fact = that
> update of first package fails does not definitely mean that i = dont want to
> update others

--resume

I know --resume, but that's not what i meant.

Imagine the situation:
emerge -p package1 package2

part1 (needed by package1)
part2 (needed by part3)
part3 (needed by package2)
part4 (needed by package2)
part5 (needed by both package1 and package2)
package1
package2

now i start "emerge package1 package2" and go to work (or sleep o= r party or sauna).

part2 fails -- some bug or misconfiguration.

currently it means that when i came back home, i see that part1 is built, but nothing more and 4-5 hours are actually just wasted.

There should be a way to have all those built when i came home:

part1 (needed by package1)
part4 (needed by package2)
part5 (needed by both package1 and package2)
package1

There should be an error message listing all others. Also, i would add them to world and then emerge so that --update would try to emerge them again, asking me about all previously failed packages when i start it, if i want to retry this time (yes, no, all, none).

--
Kind Re= gards,

Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-portage-dev@gentoo.org mailing list



--
tvali
(e-mail: "qtvali@gmail.com"; msn: " qtvali@gmail.com";
icq: "317-492-912")

=DChe e= esti internetifirma lehel kohtasin tsitaati:
If you don't do it excellently, dont do it at all. Because if it's not excellent, it won't be profitable or fun, and if you're not in business for fun or profit, what the hell are you doing here?
Robert Townsend ------=_Part_15379_30612355.1142335444123-- -- gentoo-portage-dev@gentoo.org mailing list