public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] issue on binary merge
Date: Thu, 08 Sep 2005 07:31:13 +1200	[thread overview]
Message-ID: <1126121474.7801.2.camel@sf.rout.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0509071806050.6642@tragbb.ehf.hav-fghggtneg.qr>

On Wed, 2005-09-07 at 18:33 +0200, Sascha Lucas wrote:
> Hi List,
> 
> can some explain this? Machine A+B have identical make.conf (expect in 3 
> USE-falgs), /etc/portage/*, /usr/portage, profile.
> 
> Machine A:
>   - FEATURES="buildpkg"
>   - added USE-flag "samba"
>   - emerge -uD --newuse world
>     * builds new samba package
>     * rebuilds some packages (kdebase, cups, mplayer etc.)
> 
> Machine B:
>   - mount PGKDIR of machine A via nfs to PGKDIR on machine B
>   - added USE-flag "samba"
>   - emerge -uD --newuse --usepkg world
>     * merges binary samba
>     * does not merge anything else (no binary, no ebuild )
> 
> It would be nice if I understand why emerge won't remerge binary packages 
> with changed use-flags.

It doesn't know that kdebase, cups etc need rebuilding unless you use
the --newuse option


> 
> THX,
> 
> Sascha.
> 
-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-09-07 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 16:33 [gentoo-user] issue on binary merge Sascha Lucas
2005-09-07 19:31 ` Nick Rout [this message]
2005-09-07 21:37   ` Sascha Lucas
     [not found] <4K9fO-2Cf-7@gated-at.bofh.it>
2005-09-07 20:25 ` Ian Clowes
2005-09-07 22:44   ` Sascha Lucas
     [not found] <4KeIy-2BA-9@gated-at.bofh.it>
     [not found] ` <4KeIy-2BA-7@gated-at.bofh.it>
     [not found]   ` <4Kf1U-30Z-31@gated-at.bofh.it>
2005-09-07 21:08     ` Ian Clowes
2005-09-07 23:31       ` Sascha Lucas
2005-09-08  0:17       ` Nick Rout
2005-09-08  1:02         ` Zac Medico
2005-09-08  1:19           ` Nick Rout
2005-09-08  1:03         ` Nick Rout

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=1126121474.7801.2.camel@sf.rout.dyndns.org \
    --to=nick@rout.co.nz \
    --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