Re: [gentoo-portage-dev] USE_EXPAND in profiles?
On 03/30/2016 07:22 AM, Joakim Tjernlund wrote: > On Thu, 2016-03-31 at 02:26 +1300, Kent Fredric wrote: >> On 31 March 2016 at 01:49, Joakim Tjernlund >>wrote: >>> >>> >>> I am missing something? >>> Generally I think that everything possible to do under /etc/portage should >>> be >>> doable under a profile as well. >> >> So after you ignore my other stuff: Profiles are part of the PMS >> specification, so any changes that go in there have to be EAPI >> scheduled and cried over for a bit, and probably GLEPs and stuff also. >> >> I guess portage could informally support it prior to any such >> specification materialising, but it would have to be forbidden in the >> main tree until such a specification was defined, or the portage tree >> would become PMS in-compatible. > > Yes, exactly! There is no need to use non PMS compatible features in > the gentoo tree. We hide extensions like this behind profile-formats settings in metadata/layout.conf. Please file a feature request bug for this at bugs.gentoo.org. -- Thanks, Zac
Re: [gentoo-portage-dev] USE_EXPAND in profiles?
On Thu, 2016-03-31 at 02:26 +1300, Kent Fredric wrote: > On 31 March 2016 at 01:49, Joakim Tjernlund >wrote: > > > > > > I am missing something? > > Generally I think that everything possible to do under /etc/portage should > > be > > doable under a profile as well. > > So after you ignore my other stuff: Profiles are part of the PMS > specification, so any changes that go in there have to be EAPI > scheduled and cried over for a bit, and probably GLEPs and stuff also. > > I guess portage could informally support it prior to any such > specification materialising, but it would have to be forbidden in the > main tree until such a specification was defined, or the portage tree > would become PMS in-compatible. Yes, exactly! There is no need to use non PMS compatible features in the gentoo tree. Jocke
Re: [gentoo-portage-dev] USE_EXPAND in profiles?
On 31 March 2016 at 01:49, Joakim Tjernlundwrote: > > I am missing something? > Generally I think that everything possible to do under /etc/portage should be > doable under a profile as well. So after you ignore my other stuff: Profiles are part of the PMS specification, so any changes that go in there have to be EAPI scheduled and cried over for a bit, and probably GLEPs and stuff also. I guess portage could informally support it prior to any such specification materialising, but it would have to be forbidden in the main tree until such a specification was defined, or the portage tree would become PMS in-compatible. -- Kent KENTNL - https://metacpan.org/author/KENTNL
Re: [gentoo-portage-dev] USE_EXPAND in profiles?
On 31 March 2016 at 02:21, Kent Fredricwrote: > So ruling that out first would be advised. NVM, self-- # I'm too tired to be reading and missed the profile stuff while attempting to be helpful and just was dumb instead. -- Kent KENTNL - https://metacpan.org/author/KENTNL
[gentoo-portage-dev] USE_EXPAND in profiles?
Under /etc/portage/package.use one can add: sys-libs/ntdb PYTHON_TARGETS: python2_7 net-fs/samba PYTHON_TARGETS: python2_7 But when I try to transfer this to our custom profile I get --- Invalid USE flag for 'sys-libs/ntdb' in '/var/lib/layman/transmode/profiles/gentoo64-common/package.use': 'PYTHON_TARGETS:' --- Invalid USE flag for 'net-fs/samba' in '/var/lib/layman/transmode/profiles/gentoo64-common/package.use': 'PYTHON_TARGETS:' I am missing something? Generally I think that everything possible to do under /etc/portage should be doable under a profile as well. Jocke
Re: [gentoo-portage-dev] [PATCH v3] EbuildBuild: call _record_binpkg_info earlier (bug 578204)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks. LGTM. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJW+3OvAAoJENQqWdRUGk8BM+wQAK1YIiKaS4itrZnJHAapQiCU t/01WXKQtBH8OsvIJujivaxE3kC6/F3d+5WhlNZPaNN6QLUbf9vId4fl0+pi5aqq GsVuKdSZynqXSCDkepvDeaYVjal2nrYYvaFXmKYIGMC4Z606f+iyceV8llOO+iaz lllRpu50UoDnrpNHtA/AVM6jk2qdwPN1pAatZZUyaAcn6kMECf9Oo9BJyd0OrLnw F/Wi6WKK6tZ12b4fpD+XsLZ7rgJZS1xdwCjqSYm3P0XBeqM4Ltz8xNjBJnzGxVb3 bX6iV/6MytrwIB7F5eTcr3fSLWhLgTdwr+AZtJhJfT//F3mn4dT1XkmTUV8ecc32 rBpq40R6sKUgvF0hfDCe50ejwdiWiJLm516VI27e94NDR+OetmdoOZU2ScbyoLwZ AOt+uH23RFwZzj6VRZuK6OZC3kwcYLQvc61liHlou+RQ+AGra+EhPSBB7dsggUZG O+iIAeriOGKRBDeUmBTbCaOuFebxv0HHjUBT3MvwTo4Dkwx8Z3cYhxjE+0Odgbs0 INLhA2p6O+TAwaYRIU0RZzDOA/znukmsnfn6INwNqIq0XRGNW+ocGf5kpjTm4J+M k3C5jnBa9euO/JC5ZLjjtsfag/OW3FFIze8d/R7l+Ou7ScyQ4GRW9fGbj3RbauBJ xuP6UbIUwOq3YbiZmQl/ =vm2N -END PGP SIGNATURE-