From: Andrew Gaffney <agaffney@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] perl-cleaner during stage4?
Date: Tue, 22 Jun 2010 21:09:27 -0500 [thread overview]
Message-ID: <4C216CD7.40603@gentoo.org> (raw)
In-Reply-To: <20100622135527.8586.qmail@stuge.se>
On 06/22/2010 08:55 AM, Peter Stuge wrote:
> Hi,
>
> I'm building another stage4, and since perl was updated I needed to
> run perl-cleaner --all-modules for modules to be found by other
> ebuilds. Since the package (e.g. Archive-Zip) was already installed
> (just against older perl version) the dependency didn't trigger a
> rebuild.
>
> I hacked perl-cleaner into stage4-chroot.sh, but maybe there is a
> better way to do it?
>
> I guess the same question goes also for python and python-updater.
>
>
> //Peter
>
The proper way to do it is build your own stage 1, 2, and 3 along with the stage
4, all with the same snapshot, so that you don't have "upgrades".
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Genkernel + Release Engineering Lead
next prev parent reply other threads:[~2010-06-23 2:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 13:55 [gentoo-catalyst] perl-cleaner during stage4? Peter Stuge
2010-06-23 2:09 ` Andrew Gaffney [this message]
2010-06-23 6:47 ` Peter Stuge
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=4C216CD7.40603@gentoo.org \
--to=agaffney@gentoo.org \
--cc=gentoo-catalyst@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