From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: dynamic deps, wtf are they exactly
Date: Tue, 29 Sep 2015 12:26:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20150929T140637-708@post.gmane.org> (raw)
In-Reply-To: CAJ0EP403_WuJSjpmvX5-A179SGQOJ4GewQiFZnXiGdfN4oCWtw@mail.gmail.com
Mike Gilbert <floppym <at> gentoo.org> writes:
> Basically, yes. If [R]DEPEND in /var/db/pkg is different from the
> values in the ebuilds in the tree, <at> changed-deps will select it.
> > Also, these two similar commands return different results (I have
> > bdeps=y in DEFAULT_OPTS btw):
> >
> > emerge -uND --changed-deps=y world (51 packages)
> > emerge <at> changed-deps (11 packages)
> > Do you know why those commands give different results?
> > The smaller list is a strict subset of the longer one.
> That difference is surprising; you would probably need to ask the
> portage developers to get a real answer.
I do not "own' the code underneath these options, nor would I waste my
time on what is undoubtedly broken logic. Portage and associated tools do
not have a complete description of the problem with the current VDB. A DAG
is the best way to solve the problem of these portage anomalies.
Or just rebuild @world and occasionally @system, and then cobble together
a script that hopefully finds all the other installed codes and packages....
Still, cruft (some of the old files that should have been removed at some
point) remains.
I certainly and not saying this is an easy problem to solve; all distros
suffer tremendously here. That's why many just 'reinstall' periodically.
But without a robust implementation of a DAG or something similar, deep
problems will remain unresolved and hopefully, not noticed. Many large data
centers just 'reload' entire rows of racked systems too.
These are big problems on clusters/clouds. The current approach is to build
many 'customized frameworks' for different classes of problems, on top of
poorly implemented distros with a collection of packages. That approach
works well, if the packages are relegated to one complex language and
scripts. Once a collection of codes, a package if you like, requires several
complex programming languages to compile and execute, thus crossing
framework boundaries, then the problems exponentiate, and it becomes
an admin/security mess. I do believe that the current gentoo approach is
going to be robustly application as a pristine solution for this gargantuan
cluster problem; but a DAG sort of fundamental tooling is going to be
minimally sufficient if stability is to be achieved. Clusters are already
making their way to gentoo so these problem in only going to grow.
Oddly enough, I feel like and uneducated admin in these matters. But, I do
now have several major corps that want me to be a temporary consultant
on cluster problems. We shall see. We shall see what's what.
wwr,
James
next prev parent reply other threads:[~2015-09-29 12:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 15:07 [gentoo-user] dynamic deps, wtf are they exactly Alan McKinnon
2015-09-27 15:12 ` Mike Gilbert
2015-09-27 15:28 ` Alan McKinnon
2015-09-27 16:12 ` Mike Gilbert
2015-09-29 12:26 ` James [this message]
2015-09-27 17:26 ` Michael Orlitzky
2015-09-27 19:34 ` Alan McKinnon
2015-09-27 22:21 ` Michael Orlitzky
2015-09-27 22:32 ` Alan McKinnon
2015-09-27 22:52 ` Rich Freeman
2015-09-28 0:33 ` [gentoo-user] " Martin Vaeth
2015-09-28 1:27 ` Rich Freeman
2015-09-28 7:57 ` Martin Vaeth
2015-09-28 10:55 ` Rich Freeman
2015-09-27 19:52 ` James
2015-09-27 22:41 ` Michael Orlitzky
2015-09-28 1:19 ` Martin Vaeth
2015-09-29 12:04 ` James
2015-09-30 9:41 ` Martin Vaeth
2015-09-28 0:32 ` Martin Vaeth
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=loom.20150929T140637-708@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@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