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 12:17:46 +1200	[thread overview]
Message-ID: <20050908121457.CCA8.NICK@rout.co.nz> (raw)
In-Reply-To: <431F56BD.60E8EEAC@hotmail.com>

There is no meta-info AFAIK in a binary .tar.gz, so portage does NOT
know what CFLAGS, or USE flags it is built with.

Go ahead, use quickpkg to make a binary tarball of any package on your
system, then look tat the tarball. There is nothing to indicate USE or
CFLAGS.

If you want to install binaries you have to know yourself what options
were used in the compile.


On Wed, 07 Sep 2005 22:08:13 +0100
Ian Clowes wrote:

> 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.

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-09-08  0:23 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
2005-09-08  0:17       ` Nick Rout [this message]
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=20050908121457.CCA8.NICK@rout.co.nz \
    --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