summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'decisions/summary-20101026.tex')
-rw-r--r--decisions/summary-20101026.tex39
1 files changed, 20 insertions, 19 deletions
diff --git a/decisions/summary-20101026.tex b/decisions/summary-20101026.tex
index 9b01f06..2b85c72 100644
--- a/decisions/summary-20101026.tex
+++ b/decisions/summary-20101026.tex
@@ -1,33 +1,34 @@
\summary{2010}{10}{26}
+Agenda call: ---
-\agendaitem{la files}
+Agenda announcement: ---
+
+\agendaitem{Libtool archive (.la) files}
\index{.la files}\index{package!sys-devel/libtool}
+\index{package!sys-apps/portage}
-The council decided that removing la files is the right thing to do,
- but the whole thing will be taken to the -dev ML to allow devs to
- express their opinions/objections, if any. Jorge will handle this.
+The council decided that removing la files is the right thing to do, but the
+issue will be taken to the gentoo-dev mailing list to allow developers to
+express their opinions/objections, if any. \dev{jmbsvicetto} will handle this.
- The removal will only happen after portage-2.1.9 or later is
- stabilized, since this is the first version that can fix la files
- automatically.
+The removal will only happen after portage-2.1.9 or later has been
+stabilized, since this is the first version that can fix la files automatically.
- At that time, a news item will be released to inform users on how to
- fix any issues that may arise from the removal.
+At that time, a news item will be released to inform users on how to fix any
+issues that may arise from the removal.
\agendaitem{EAPI 4}
-\index{EAPI!4}\index{REQUIRED_USE}
-
-few_ suggested finalizing EAPI 4 with the features currently
- implemented in portage (\bug{273620}).
+\index{EAPI!4}\index{REQUIRED_USE}\index{PMS}
- we agreed that this is a good idea, as long as a spec list is built
- and PMS patches are written for all the features.
+Sebastian Luther (few_) suggested finalizing EAPI 4 with the features currently
+implemented in portage (\bug{273620}).
- ferringb will write documentation for REQUIRED_USE.
+The council agreed that this is a good idea, as long as a specification list is
+built and PMS patches are written for all the features.
- the council will finalize things in the next meeting. people
- responsible for EAPI 4 should be pinged beforehand so they can attend
- that meeting.
+\dev{ferringb} will write documentation for REQUIRED_USE. The council will
+finalize things in the next meeting. People responsible for EAPI 4 should be
+pinged beforehand so they can attend that meeting.