public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sascha Lucas <sascha.lucas@rus.uni-stuttgart.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] issue on binary merge
Date: Thu, 8 Sep 2005 01:31:02 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0509080117410.7611@tragbb.ehf.hav-fghggtneg.qr> (raw)
In-Reply-To: <431F56BD.60E8EEAC@hotmail.com>

>> emerge -1 --usepkg --pretend --verbose pkg_spec_from_equery
>>
>> then the change in USE-Flags are showen and my _correct_ binarys are used.
>>
>
> There's probably a good reason for it being the way it is, but it
> doesn't sound as transparent as we might like.

yes may be... if so, I would like to know the reason :-)


> A further interesting scenario might be to have a binary package
> available built with different USE flags to those on the target machine,
> and seeing if it gets installed or not.  I guess it shouldn't.  But then
> there's the CFLAGS issue as well, and I'm even more unsure how that's
> supposed to be handled.

If you build a binary with different USE flags then on the target it 
would be merged as ebuild and not as binary. But this seems only to work 
with --usepkg not with --getbinpkg. ?? CFLAGS handling is done in the same 
way like USE flags. You can use the tbz2tool to split your binary into 
data (tar) and info (text). In this info-text is every thing stored like 
USe, CFALGS, ....

> I'm still pretty new to Gentoo, but is this perhaps related to the
> feature I've read about (and maybe misremembered) regarding only
> packages that you explicity emerge going into world (dependencies
> don't)?  I wonder if you'd see different results if you explicitly
> emerged cups rather than it having been implicity emerged due to a
> dependency.  By doing the emerge you described you've 'promoted' those
> packages from implicit to explicit emerge.

Hm... yes every time you type emege .... it will be recorded in the 
world-file, expect emerge --oneshot (-1)... so my explicit merge will not 
be recorded in world it stays what it was before (world or dependency).

So I understand --usepkg in this way to use binary if all USE/C flags etc 
match. If not fallback to ebuilds. So I know I have the right binary pkgs, 
why does:

emerge -uDpv --newuse world

and

emerge -uDpv --newuse --usepkg world

show different results?

Sascha.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-09-07 21:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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     ` [gentoo-user] issue on binary merge Ian Clowes
2005-09-07 23:31       ` Sascha Lucas [this message]
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
     [not found] <4K9fO-2Cf-7@gated-at.bofh.it>
2005-09-07 20:25 ` Ian Clowes
2005-09-07 22:44   ` Sascha Lucas
2005-09-07 16:33 Sascha Lucas
2005-09-07 19:31 ` Nick Rout
2005-09-07 21:37   ` Sascha Lucas

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=Pine.LNX.4.63.0509080117410.7611@tragbb.ehf.hav-fghggtneg.qr \
    --to=sascha.lucas@rus.uni-stuttgart.de \
    --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