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 EA805138334 for ; Mon, 13 Aug 2018 16:58:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D232FE0822; Mon, 13 Aug 2018 16:58:10 +0000 (UTC) Received: from sonic315-13.consmr.mail.bf2.yahoo.com (sonic315-13.consmr.mail.bf2.yahoo.com [74.6.134.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4073CE0801 for ; Mon, 13 Aug 2018 16:58:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1534179489; bh=sw2L0/hp2TWH9kmG2lbyIdM8T2s2pemQPnjt05rwg1k=; h=Subject:From:To:References:Date:In-Reply-To:From:Subject; b=pLwhfc18PqWUvPO1STJc8xswEQ5th2SQiuQNEJZTROb6JTDKiRY82MD2YN5uISMjd1YLPCPgAOzEknRd3G4bMcbjgRdRS7z+Y93Z1kvdnvd7UJyQf1lLEJpsLa4FCWHS++j75fMMRibKNjaE0rD7SeN/fEmtP381hfLrYZLhMXzTGUHp0qh9txnSieCm7nCkDS3nY8wGGlOyOP4DS76aAGsg6q1Ixo90md9f25mCYZQhsTNDCD2D1CHyweeV3thmsODOEIdteAwOFMB99ehel8UEXKM3ZZLFCQqgepoU8njnnbLfxQFzg1GWd5UEGuxLmZAmknWp4YY/UacSr6ebJA== X-YMail-OSG: c3vMpOIVM1n2m5LXRb49WAj6lMzk2JkFemw5O_Ofo44BlD523W0ozYKK4Ej5xoX 5XvK2EmkzDRQncIeZiEf1aB9gDOHgBkn0X6VZHxyVy2co7tJDzO6aqfx_uVfFKjU_Fwz7N08VvN6 OEHTGiyQs51XhqDJDT3jYNn6JsNXLDxDmq8DzoXimozjbx6w8FBhOyDFF1vKsO06whcmIo0CNpdd 3YaD0zu5VilzObz22Cl7IjA0fOUnwLI3e6J2mDv.qPEEESY2fsEFp0QMCbj.AxUjLoHmSSHEdQHl hA_wAgekTXvMOm_sN2TGI41i9VSBgwEIWfw3rrRu0HGBF1DUN5Xl_.LUqRNyAAqtbL7w_qnIXAlT YTUmklGiMKhexgCCg3Oh50P2uJqtLCV8R8P5j9xDnQQED0qzTFctiHUg1OFaLGWiCQqssuCYPk.z RywMWCXVuPnQd5LBpwNulyqSZljgn0FTwK_SYG0lXcVkgx8Ty6jJNW7uj8y_b.w09ZrGe1CzMot. 0IRH.4acyTdD7qPm_P8uiQCQjCvfILClUTJPFaseB6GsfbYLV3kxLybp4sCe2XYsawyB2t.sOJpX rDPfi6SB6JsBLl0iOYw4nDuo_AiFy9eJLHiIIDwj50emzjwdzWwiWoO87wVunet2TssVV_FUghvk fVfJym4ceOGkQWgduHDutOv4D_MGJcLpUY3.2lLLV0X.nPwsoMPsdhMNnmJRKib88MdNBYB0U68x PQlbd6pVgAcyzeoazZSIX95KtwreNAmXuSerLIg5BzD2068yzbJ3ruiqDKl9LrbivZAddSkvfkk. qUdRZ2KRYxRhfPI0U5EjG6KnyYWvgi2LnB0rimRi1Pc_xqpnfaxWSLMumVKhG0AmXwpPnwRPSSGL j79XUW8uRU_IlQiCHN_0f3p4UEvSUNhJxghsD8AQVCDDUTtI6gWOXMkKikYJE1PcR8Nmuo3FCsbO rurF8rp3hy9hIBasEpakqR5Pi3TqlDKkrkfaNmDJNafYw9dz0ajvMuiGBOp9.dI.9EwmWaRxqVLp y9dYkIw2P9wl_jg8- Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Mon, 13 Aug 2018 16:58:09 +0000 Received: from 72.185.251.10 (EHLO [192.168.1.52]) ([72.185.251.10]) by smtp409.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID c8129f33e25cf2c89e9dd73b7a50c087; Mon, 13 Aug 2018 16:58:07 +0000 (UTC) Subject: Re: [gentoo-user] flag icu From: james To: gentoo-user@lists.gentoo.org References: <5a8de66b71743b58865795587093b718@troglodyte.be> <70462ac2-5328-e32e-450b-fbfea09c72e6@verizon.net> Openpgp: preference=signencrypt Message-ID: <2cb61d3d-14c9-d5e1-1a82-93dfbf34e1cd@verizon.net> Date: Mon, 13 Aug 2018 12:58:06 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 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 In-Reply-To: <70462ac2-5328-e32e-450b-fbfea09c72e6@verizon.net> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Archives-Salt: b161ce79-05da-45d5-b0e3-148744801ab1 X-Archives-Hash: 39659dc5efc05360a05f601b7756ee5a On 08/13/18 11:47, james wrote: > On 08/13/18 11:36, Corentin �Nado� Pazdera wrote: >> August 13, 2018 4:31 PM, "james" wrote: >> >>> Any hints on a systematic by system parsing this sort of minimized-flag >>> data : >>> >>> [12] default/linux/amd64/17.0 (stable) * >>> >>> would be keenly appreciated. "eselect profile list" is great. but >>> I need it per many different architectures and do not have one >>> of each of the systems I need to experiment on. How are those flag_sets >>> discovered in some sort of systematic approach? >> >> Hi, >> >> I don't know if this will be of any help but I made a script [1] recently to analyze the >> inheritance of system set. >> It may have a few bugs I did that for learning the inner workings of profiles mainly. >> It should'nt need much work to make it print USE flags details >> >> [1] https://gist.github.com/nado/44b392b50c0b71a7e22b98d6909bfa72 >> >> Best regards, >> -- >> Corentin �Nado� Pazdera >> >> > > > Hey thanks, > > I'm testing now an it has given me a few ideas to extend the > capabilities.... > > > James > Here's what I got running your script:: /etc # /root/profile-explorer.sh --- Invalid atom in /etc/portage/package.use/explored-packages: /usr/portage/profiles/base/packages --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-apps/baselayout-2 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-apps/findutils-4.4 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-devel/patch-2.7 --- Invalid atom in /etc/portage/package.use/explored-packages: /usr/portage/profiles/default/linux/packages --- Invalid atom in /etc/portage/package.use/explored-packages: /usr/portage/profiles/base/packages --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-apps/baselayout-2 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-apps/findutils-4.4 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-devel/patch-2.7 --- Invalid atom in /etc/portage/package.use/explored-packages: /usr/portage/profiles/default/linux/packages Manually looking a the less /etc/portage/package.use/explored-packages: /usr/portage/profiles/base/packages I see: # Old ICU is unsupported. ICU 58 only remains for 13.0 based profiles. =sys-apps/baselayout-2 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-apps/findutils-4.4 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-devel/patch-2.7 --- Invalid atom in /etc/portage/package.use/explored-packages: /usr/portage/profiles/default/linux/packages --- Invalid atom in /etc/portage/package.use/explored-packages: /usr/portage/profiles/base/packages --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-apps/baselayout-2 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-apps/findutils-4.4 --- Invalid atom in /etc/portage/package.use/explored-packages: *>=sys-devel/patch-2.7 --- Invalid atom in /etc/portage/package.use/explored-packages: /usr/portage/profiles/default/linux/packages [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for dev-libs/icu-60.2: U I + + abi_x86_32 : 32-bit (x86) libraries - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces - - doc : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally + + examples : Install examples, usually source code - - static-libs : Build static versions of dynamic libraries as well Which begs the Q1} can I get rid of the flag icu? What are consequences, as a baseline system flag, of it's removal ? less /usr/portage/profiles/base/packages show me more of what the @system set contains. Very interesting and useful. I'm thinking of aggregation of those listed packages and some basic (ascii) table form (equery,emerge, eix) parsed listing of the default and current flag settings. A "verification" tool if you like. Surely it would help if this info was (is?) more readily available and organized for folks that need a systematic approach, like heterogeneous HPC clusters. The tools exist for 'ad-hoc' and one off, but more of an organized representation at least at the set level. I feel like there is an existing tool that can yield all of this information, as it is on a current system. I've read where there are efforts to clean up the packages and default flags used in @system, so the bare minimum list per arch/profiles would ultimately be a useful listing, particular for my HPC. In HPC less is always faster and better, as it is in security and so many more aspects of CS. Obviosly, I have a few things to fix on this (fragile) system, but that'll happen as I'm at the beginning stages of auto_installs of minimized systems. What are your plans for you little script? Just to match equery uses and such? Here's a cutie: /usr/portage/profiles/default/linux/amd64/package.use.mask # Mike Frysinger (08 May 2016) # This target supports VTV #547040. >=sys-devel/gcc-4.9 -vtv # Mike Frysinger (21 Oct 2014) # This target supports ASAN/etc... #504200. sys-devel/gcc -sanitize And where was it that the processor/arch flags are now listed? tia, James cat