From: tvali <qtvali@gmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Few things, which imho would make portage better
Date: Tue, 14 Mar 2006 13:53:07 +0200 [thread overview]
Message-ID: <cea53e3c0603140353o7f85f16bx@mail.gmail.com> (raw)
In-Reply-To: <cea53e3c0603140324k691219cbo@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4598 bytes --]
I did think about some priorities too, so that it could be perfect for me.
It should be possible to add package with a priority. I will give you an use
case and explanation how i would use portage.
emerge --justadd kdebase-meta kicker --priority 10
emerge --justadd kdenetwork-meta kdeutils-meta kdeadmin-meta --priority 9
emerge --justadd kdeedu-meta kdetoys-meta kdegames-meta kdeartwork-meta
--priority 1
emerge --justadd koffice-meta kdegraphics-meta kdemultimedia-meta --priority
5
emerge --justadd kdewebdev-meta kdevelop htmltidy kompare cervisia
--priority 7
emerge --justadd kdepim-meta --priority 3
emerge --justadd kdeaddons-meta kde-meta --priority 20
emerge --changepriority kdeaddons-meta kde-meta --priority 0
Now, when i run emerge --update, it should:
* Sort packages in such order that packages with highest priority would be
installed as soon as possible
* Start installing
* If something goes wrong, then skip this package and all, which depend on
it. This should be optional, if those, which dont depend on it, but are
needed by same package, will stay in their positions (go to end of same
priority packages) or go to end.
When i need to use my computer and need much resources, i will press ctrl-c,
use it, then start (continue) emerge --update.
2006/3/14, tvali <qtvali@gmail.com>:
>
> 2006/3/14, Simon Stelling <blubb@gentoo.org>:
> >
> > 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 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 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 to 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")
>
> Ühe 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
>
--
tvali
(e-mail: "qtvali@gmail.com"; msn: "qtvali@gmail.com";
icq: "317-492-912")
Ühe 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
[-- Attachment #2: Type: text/html, Size: 6606 bytes --]
next prev parent reply other threads:[~2006-03-14 11:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 11:02 [gentoo-portage-dev] Few things, which imho would make portage better tvali
2006-03-14 11:10 ` Simon Stelling
2006-03-14 11:24 ` tvali
2006-03-14 11:53 ` tvali [this message]
2006-03-14 12:14 ` tvali
2006-03-14 13:19 ` Devon Miller
2006-03-14 13:25 ` tvali
2006-03-14 13:50 ` tvali
2006-03-14 14:33 ` tvali
2006-03-14 15:04 ` Brian
2006-03-14 15:32 ` tvali
2006-03-14 16:21 ` Brian
2006-03-15 0:33 ` esearch integration [was Re: [gentoo-portage-dev] Few things, which imho would make portage better] Brian Harring
2006-03-15 14:20 ` tvali
2006-03-15 14:21 ` tvali
2006-03-15 0:37 ` sync suggestions " Brian Harring
2006-03-15 14:18 ` tvali
2006-03-14 13:21 ` [gentoo-portage-dev] Few things, which imho would make portage better tvali
2006-03-14 13:35 ` Marius Mauch
2006-03-14 14:52 ` tvali
2006-03-15 0:29 ` sql based cache [was Re: [gentoo-portage-dev] Few things, which imho would make portage better] Brian Harring
2006-03-14 14:44 ` [gentoo-portage-dev] Few things, which imho would make portage better Alec Warner
2006-03-14 15:03 ` tvali
2006-03-14 15:53 ` Johannes Fahrenkrug
2006-03-14 16:24 ` tvali
2006-03-14 13:50 ` Marius Mauch
2006-03-14 15:18 ` solar
2006-03-14 16:35 ` tvali
2006-03-14 18:26 ` tvali
2006-03-14 18:30 ` Grant Goodyear
2006-03-14 18:46 ` tvali
2006-03-14 18:49 ` Grant Goodyear
2006-03-14 14:50 ` felix
2006-03-14 13:44 ` Marius Mauch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cea53e3c0603140353o7f85f16bx@mail.gmail.com \
--to=qtvali@gmail.com \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox