From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Stupid question regarding 'fixpackages'
Date: Mon, 20 Oct 2003 17:31:38 +0200 [thread overview]
Message-ID: <20031020173138.2da98efa.genone@gentoo.org> (raw)
In-Reply-To: <200310202301.22990.jasonbstubbs@mailandnews.com>
[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]
On 10/20/03 Jason Stubbs wrote:
> On Monday 20 October 2003 20:12, Marius Mauch wrote:
> > On 10/20/03 Joachim Breuer wrote:
> > > Now, my question is: Shouldn't fixpackages 'stabilize', i.e. not
> > > perform global updates it has already performed? The way it is now
> > > I'd hate to think what an upgrade will be like a year or two from
> > > now... If this 'stabilizing' cannot be done I'd like to know for
> > > what reason, perhaps I'd want to take a look whether there really
> > > isn't an useful optimization.
> >
> > Well, there are different opinions on that. I'd like to make the
> > fixpackages script behave the same way as FEATURES="fixpackages",
> > but there is a reason not to do this: the do_upgrade function which
> > actually does all the work for fixpackages (and more) maintains a
> > mtime table when it runs, but it is run by emerge and fixpackages.
> > The problem now is that when do_upgrade runs from emerge without
> > FEATURES="fixpackages" it updates the mtime table, that means the
> > information would be wrong for fixpackages. I guess in the end we
> > will have to add another mtime table for fixpackages to fix this
> > issue.
>
> I hate to sound lame, but I'm not sure I followed that correclty.
> fixpackages, when called using FEATURES, only fixes the packages that
> the emerge process touches? And, when calling fixpackages directly, it
> processes all packages? Is that correct? If not, can you please
> explaing the difference between the two?
No, both versions touch all packages, the difference is that the
FEATURES thing will only use updates files (in
/usr/portage/profiles/updates) that were changed since the last run
while the fixpackages script always uses all update files for the
reasons I outlined above.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-10-20 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 10:28 [gentoo-dev] Stupid question regarding 'fixpackages' Joachim Breuer
2003-10-20 11:12 ` Marius Mauch
2003-10-20 11:51 ` Joachim Breuer
2003-10-20 12:48 ` Marius Mauch
2003-10-20 14:01 ` Jason Stubbs
2003-10-20 15:31 ` Marius Mauch [this message]
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=20031020173138.2da98efa.genone@gentoo.org \
--to=genone@gentoo.org \
--cc=gentoo-dev@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