From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recent changes to install procedure
Date: Sat, 03 Aug 2019 17:04:17 +0100 [thread overview]
Message-ID: <1830065.4ShgvUamWB@localhost> (raw)
In-Reply-To: <d02d05af-a44d-99f8-9734-dd422234125e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
On Saturday, 3 August 2019 16:45:07 BST Dale wrote:
> Walter Dnes wrote:
> > On Sat, Aug 03, 2019 at 12:24:51AM -0400, Walter Dnes wrote
> >
> >> I'll insert CHOST and MAKEOPTS to play safe. Any other gotchas in
> >> recent installs?
> >>
> > So far so good. The basic system is installed and booting. One
> >
> > question... can I just set the "bindist" USE flag globally. On a basic
> > text install (Xorg not installed yet) in package.use I've already set...
> >
> > dev-libs/openssl bindist
> > net-misc/openssh bindist
> > net-wireless/iw bindist
> > net-wireless/wpa_supplicant bindist
>
> Just out of curiosity I did a euse -i bindist. It seems what that flag
> does sort of depends on the package it is set for. You may want to
> investigate what it will do on those packages before setting it
> globally. Of course, if the majority of the time you want that enabled,
> you could disable it for those packages where it does something you
> don't want but have the default set to on. Whichever is easier.
>
> Hope that helps.
>
> BTW, I moved my tree and such to /var/cache/portage/ a few years ago.
> At the time, that was the location most supported but I guess time
> changed things and they picked another location. Other than knowing
> what location for emerge and friends to put and look for the related
> items, it doesn't matter where one puts it really, as long as
> permissions are correct.
>
> Dale
>
> :-) :-)
Unless you're building binaries to redistribute it doesn't make sense to set
it globally. I vaguely recall something going sideways with openssl when I
had this flag set in the past, so I've left it unset since.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-03 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 4:24 [gentoo-user] Recent changes to install procedure Walter Dnes
2019-08-03 6:56 ` Neil Bothwick
2019-08-03 16:27 ` [gentoo-user] " Ian Zimmerman
2019-08-03 16:31 ` Dale
2019-08-03 17:10 ` Ian Zimmerman
2019-08-03 17:18 ` Neil Bothwick
2019-08-03 15:32 ` [gentoo-user] " Walter Dnes
2019-08-03 15:45 ` Dale
2019-08-03 16:04 ` Mick [this message]
2019-08-03 16:15 ` Dale
2019-08-03 17:13 ` Walter Dnes
2019-08-03 17:35 ` Dale
2019-08-03 18:39 ` Walter Dnes
2019-08-03 20:45 ` Neil Bothwick
2019-08-03 16:18 ` [gentoo-user] " Nikos Chantziaras
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=1830065.4ShgvUamWB@localhost \
--to=michaelkintzios@gmail.com \
--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