Hi, So.e info regarding the next profile 17.1 of Gentoo:
https://archives.gentoo.org/gentoo-dev/message/1bb98efdb36a85c35d3f0a5597d7838e In case we need to prepare. Cheers, Ryuno-Ki -------- Ursprüngliche Nachricht -------- Von: "André Jaenisch" <[email protected]> Gesendet: 6. Dezember 2017 07:13:50 MEZ An: Sabayon Dev ML <[email protected]> Betreff: Re: [sabayon-dev] [Proposal] Sabayon profile Hi, for reference, it is about https://pastebin.com/JK24WMDC which I picked on a Gentoo chat recently. Kind regards Ryuno-Ki -------- Ursprüngliche Nachricht -------- Von: Geaaru <[email protected]> Gesendet: 4. Dezember 2017 05:42:05 MEZ An: Sabayon Dev ML <[email protected]> Betreff: [sabayon-dev] [Proposal] Sabayon profile Hi guys, I read just now post on IRC about migration to Gentoo Profile Version 17.0. About this, as introduces in some post to IRC I'm currently try to review work done about Docker build image process. On review process I tried to rebuild docker layers without replace directly /etc/portage directory with /opt/sabayon-build/conf/${ARCH} but with creation of sabayon profile. # eselect profile list Available profile symlink targets: [1] default/linux/amd64/13.0 ... [12] default/linux/amd64/13.0/sabayon * On my experiment I create an hook on portage sync that use directly directory /usr/portage/profiles but I see that these changes could be done directly to sabayon-distro overlay. In this way, users that would be create custom repository with few changes could be configure sabayon profile and use classic /etc/portage directory for customize useflag, etc. or also Gentoo users that want use Sabayon base environment (use flags, keywords, etc.) could be configure it simply with some steps after dowload correct layman. However, currently there are some problems on this solution that doesn't permit a clean migration to Gentoo Profiles: * set PYTHON_TARGETS / USE_PYTHON configured on make.deafults under profile seems doesn't catch correctly, must be set on /etc/portage/make.conf * current PMS engine doesn't support package.mask with repos. Example: sys-devel/gcc::gentoo, for this masking is required push file under /etc/portage/package.mask/. Some things (at least seems) for .env files. So, also with these limitations I think that could be a fine solutions and probably could be take opportunity for migrate to gentoo profile 17 for test this. If are present these variables: GENTOO_PROFILE_NAME="/sabayon" SABAYON_PROFILE_TARGETS="/systemd /sabayon/amd64" Code for create targets and file under /etc/portage (from build project) is here: https://github.com/geaaru/sabayon-reload/blob/master/sabayon-stuff/comm ons.sh#L218 I'm currently testing this solution with sabayon-stage3 docker image and with some fix it seems works fine. WDYT? G.
