From: Thomas Anderson <gentoofan23@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: [gentoo-council] Council summary for Meeting on December 11th, 2008
Date: Tue, 17 Feb 2009 13:58:17 -0500 [thread overview]
Message-ID: <20090217185817.GA420@dodo.hsd1.nj.comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Attached. I could probably use a little description for DEFINED_PHASES
from those who know more about it than myself. That'd be appreciated.
Thanks,
Thomas
--
---------
Thomas Anderson
Gentoo Developer
/////////
Areas of responsibility:
AMD64, Secretary to the Gentoo Council
---------
[-- Attachment #2: councilsummary-20081211.txt --]
[-- Type: text/plain, Size: 1326 bytes --]
Roll Call:
==========
Betelgeuse: here
Cardoe: absent
dertobi123: here
dev-zero: here
dberkholz: here
Halcy0n: here
lu_zero: here
Meeting Topics:
===============
Technical Issues:
- Label profiles with EAPI for compatibility checks:
Should there be labels in the profiles telling package managers what
EAPI the profile uses. This proposal raised some concerns that
developers would modify current profiles and bump the EAPI which would
harm users' systems.
Conclusion:
Profile EAPI files are approved for use in gentoo-x86 profiles.
The file for use in profiles is 'eapi'. All current profiles
are EAPI="0" and only new EAPIs can be marked with the profile
EAPI markers. Any developer profiles can be marked with a new
EAPI.
- Retroactive EAPI change: Call ebuild functions from trusted working
directory:
Donnie(dberkholz) commented that it may not be needed to add something
to EAPI=0 that is in all the Package Managers.
Conclusion:
Approved. This change applies to all current EAPIs(0,1,2).
- Metadata variable for DEFINED_PHASES
Conclusion:
Approved. Infra will do a full regen of the metadata cache once
portage has support for it.
next reply other threads:[~2009-02-17 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 18:58 Thomas Anderson [this message]
2009-02-17 19:04 ` [gentoo-council] Council summary for Meeting on December 11th, 2008 Ciaran McCreesh
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=20090217185817.GA420@dodo.hsd1.nj.comcast.net \
--to=gentoofan23@gentoo.org \
--cc=gentoo-council@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