From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5675E138334 for ; Mon, 13 Aug 2018 17:14:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4BA62E086A; Mon, 13 Aug 2018 17:14:49 +0000 (UTC) Received: from Sindri.troglodyte.be (sindri.troglodyte.be [51.15.219.152]) by pigeon.gentoo.org (Postfix) with ESMTP id A9F3CE0827 for ; Mon, 13 Aug 2018 17:14:48 +0000 (UTC) Received: from cloud.troglodyte.be (localhost [127.0.0.1]) by Sindri.troglodyte.be (Postfix) with ESMTPSA id 8D5BE800B4 for ; Mon, 13 Aug 2018 19:14:24 +0200 (CEST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Date: Mon, 13 Aug 2018 17:14:24 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: RainLoop/1.12.0 From: "=?utf-8?B?Q29yZW50aW4g4oCcTmFkb+KAnSBQYXpkZXJh?=" Message-ID: Subject: Re: [gentoo-user] flag icu To: gentoo-user@lists.gentoo.org In-Reply-To: <2cb61d3d-14c9-d5e1-1a82-93dfbf34e1cd@verizon.net> References: <2cb61d3d-14c9-d5e1-1a82-93dfbf34e1cd@verizon.net> <5a8de66b71743b58865795587093b718@troglodyte.be> <70462ac2-5328-e32e-450b-fbfea09c72e6@verizon.net> X-Archives-Salt: 3bcee9ee-b5c5-4fa4-a4bd-01e1eb822d4d X-Archives-Hash: 42cbd6f3c685af9a0249fe5ba42d8440 August 13, 2018 6:58 PM, "james" wrote:=0A=0A> Here'= s what I got running your script::=0A> =0A> /etc # /root/profile-explorer= .sh=0A> --- Invalid atom in /etc/portage/package.use/explored-packages:= =0A> /usr/portage/profiles/base/packages=0A> --- Invalid atom in /etc/por= tage/package.use/explored-packages:=0A> *>=3Dsys-apps/baselayout-2=0A> --= - Invalid atom in /etc/portage/package.use/explored-packages:=0A> *>=3Dsy= s-apps/findutils-4.4=0A> --- Invalid atom in /etc/portage/package.use/exp= lored-packages:=0A> *>=3Dsys-devel/patch-2.7=0A> --- Invalid atom in /etc= /portage/package.use/explored-packages:=0A> /usr/portage/profiles/default= /linux/packages=0A> --- Invalid atom in /etc/portage/package.use/explored= -packages:=0A> /usr/portage/profiles/base/packages=0A> --- Invalid atom i= n /etc/portage/package.use/explored-packages:=0A> *>=3Dsys-apps/baselayou= t-2=0A> --- Invalid atom in /etc/portage/package.use/explored-packages:= =0A> *>=3Dsys-apps/findutils-4.4=0A> --- Invalid atom in /etc/portage/pac= kage.use/explored-packages:=0A> *>=3Dsys-devel/patch-2.7=0A> --- Invalid = atom in /etc/portage/package.use/explored-packages:=0A> /usr/portage/prof= iles/default/linux/packages=0A> =0A> Manually looking a the=0A=0ASeems we= ird, also no need to run it as root...=0AHere's my output for comparison = :=0A=0A```=0A% ./profile-explorer.sh=0A[+] EROOT : /=0A[+] PORTDIR : /var= /db/repos/gentoo=0A[+] CURPROFILE: default/linux/amd64/17.0=0A[+] EAPI : = 5=0A=0A[+] packages (@system)=0A/var/db/repos/gentoo/profiles/base/packag= es=0A/var/db/repos/gentoo/profiles/default/linux/packages=0A```=0A=0AAnd = the `explored-packages` file should symply contain a copy of the differen= t inherited packages=0Afiles.=0A=0A> less /etc/portage/package.use/explor= ed-packages:=0A> /usr/portage/profiles/base/packages=0A> =0A> I see:=0A> = # Old ICU is unsupported. ICU 58 only remains for 13.0 based profiles.=0A= > =0A> But the system = has::=0A> =0A> [I] dev-libs/icu .... 60.2=0A> =0A> equery uses icu=0A> = =0A> gives me similar info:=0A> =0A> --- Invalid atom in /etc/portage/pac= kage.use/explored-packages:=0A> /usr/portage/profiles/base/packages=0A> -= -- Invalid atom in /etc/portage/package.use/explored-packages:=0A> *>=3Ds= ys-apps/baselayout-2=0A> --- Invalid atom in /etc/portage/package.use/exp= lored-packages:=0A> *>=3Dsys-apps/findutils-4.4=0A> --- Invalid atom in /= etc/portage/package.use/explored-packages:=0A> *>=3Dsys-devel/patch-2.7= =0A> --- Invalid atom in /etc/portage/package.use/explored-packages:=0A> = /usr/portage/profiles/default/linux/packages=0A> --- Invalid atom in /etc= /portage/package.use/explored-packages:=0A> /usr/portage/profiles/base/pa= ckages=0A> --- Invalid atom in /etc/portage/package.use/explored-packages= :=0A> *>=3Dsys-apps/baselayout-2=0A> --- Invalid atom in /etc/portage/pac= kage.use/explored-packages:=0A> *>=3Dsys-apps/findutils-4.4=0A> --- Inval= id atom in /etc/portage/package.use/explored-packages:=0A> *>=3Dsys-devel= /patch-2.7=0A> --- Invalid atom in /etc/portage/package.use/explored-pack= ages:=0A> /usr/portage/profiles/default/linux/packages=0A> [ Legend : U -= final flag setting for installation]=0A> [ : I - package is installed wi= th flag ]=0A> [ Colors : set, unset ]=0A> * Found these USE flags for dev= -libs/icu-60.2:=0A> U I=0A> + + abi_x86_32 : 32-bit (x86) libraries=0A> -= - debug : Enable extra debug codepaths, like asserts and extra=0A> outpu= t. If=0A> you want to get meaningful backtraces see=0A> =0A> https://wiki= .gentoo.org/wiki/Project:Quality_Assurance/Backtraces=0A> - - doc : Add e= xtra documentation (API, Javadoc, etc). It is=0A> recommended to=0A> enab= le per package instead of globally=0A> + + examples : Install examples, u= sually source code=0A> - - static-libs : Build static versions of dynamic= libraries as well=0A> =0A> Which begs the Q1} can I get rid of the flag = icu? What are=0A> consequences, as a baseline system flag, of it's remova= l ?=0A> =0A> less /usr/portage/profiles/base/packages=0A> show me more of= what the @system set contains. Very interesting and=0A> useful. I'm thin= king of aggregation of those listed packages=0A> and some basic (ascii) t= able form (equery,emerge, eix) parsed listing=0A> of the default and curr= ent flag settings. A "verification" tool=0A> if you like. Surely it would= help if this info was (is?) more readily=0A> available and organized for= folks that need a systematic approach, like=0A> heterogeneous HPC cluste= rs. The tools exist for 'ad-hoc' and one off,=0A> but more of an organize= d representation at least at the set level.=0A> =0A> I feel like there is= an existing tool that can yield all of this=0A> information, as it is on= a current system. I've read where there are=0A> efforts to clean up the = packages and default flags used in @system,=0A> so the bare minimum list = per arch/profiles would ultimately be=0A> a useful listing, particular fo= r my HPC. In HPC less is always faster=0A> and better, as it is in securi= ty and so many more aspects of CS.=0A> =0A> Obviosly, I have a few things= to fix on this (fragile) system, but=0A> that'll happen as I'm at the be= ginning stages of auto_installs of=0A> minimized systems. What are your p= lans for you little script?=0A> =0A> Just to match equery uses and= such?=0A> =0A> Here's a cutie:=0A> /usr/portage/profiles/default/linux/a= md64/package.use.mask=0A> =0A> # Mike Frysinger (08 M= ay 2016)=0A> # This target supports VTV #547040.=0A>> =3Dsys-devel/gcc-4.= 9 -vtv=0A> =0A> # Mike Frysinger (21 Oct 2014)=0A> # = This target supports ASAN/etc... #504200.=0A> sys-devel/gcc -sanitize=0A>= =0A> And where was it that the processor/arch flags are now listed?=0A> = =0A> tia,=0A> James=0A> cat=0A=0ATo check impact on negating icu on your = system : `USE=3D"-icu" emerge -puDU --with-bdeps=3Dy world`=0A=0AAnd conc= erning processor/arch flags I=E2=80=99d suggest keep exploring profiles, = take a look at=0Amake.defaults files.=0AHere the different files you can = find according to PMS=0Ahttps://dev.gentoo.org/~ulm/pms/head/pms.html#x1-= 430005.2=0A=0A--=0ACorentin =E2=80=9CNado=E2=80=9D Pazdera