summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas K. Hüttel <dilfridge@gentoo.org>2017-05-07 15:18:49 +0200
committerAndreas K. Hüttel <dilfridge@gentoo.org>2017-05-07 15:18:49 +0200
commit34d1532d19ba8904da5963b5d85ad70106c67a64 (patch)
tree2c2e1558eb801b75ad962bd57a264059e20b6ee5 /decisions
parentConvert 4/2017 (diff)
downloadcouncil-34d1532d19ba8904da5963b5d85ad70106c67a64.tar.gz
council-34d1532d19ba8904da5963b5d85ad70106c67a64.tar.bz2
council-34d1532d19ba8904da5963b5d85ad70106c67a64.zip
Improve 2/2009
Diffstat (limited to 'decisions')
-rw-r--r--decisions/decisions.bux2
-rw-r--r--decisions/decisions.ded3
-rw-r--r--decisions/decisions.kilepr54
-rw-r--r--decisions/decisions.mlf2
-rw-r--r--decisions/decisions.mls2
-rw-r--r--decisions/decisions.mlt2
-rw-r--r--decisions/documents.tex188
-rw-r--r--decisions/summary-20090122.tex1
-rw-r--r--decisions/summary-20090212.tex115
9 files changed, 283 insertions, 86 deletions
diff --git a/decisions/decisions.bux b/decisions/decisions.bux
index 67b1ba7..2dcfd52 100644
--- a/decisions/decisions.bux
+++ b/decisions/decisions.bux
@@ -46,6 +46,8 @@ Code of Conduct!extent;Code of Conduct!enforcement
council!appeal process
239560
package!sys-apps/portage;GLSA!200810-02;CVE!2008-4394;ebuild!working directory
+250077
+prepalldocs;PMS
256453
council!meeting!process;council!meeting!agenda
273620
diff --git a/decisions/decisions.ded b/decisions/decisions.ded
index 5b8713c..2102bbe 100644
--- a/decisions/decisions.ded
+++ b/decisions/decisions.ded
@@ -40,6 +40,9 @@ Donnie Berkholz
dertobi123
Tobias Scherbaum
+dev-zero
+Tiziano Müller
+
dsd
Daniel Drake
diff --git a/decisions/decisions.kilepr b/decisions/decisions.kilepr
index d9ebe60..eaa2f49 100644
--- a/decisions/decisions.kilepr
+++ b/decisions/decisions.kilepr
@@ -4,7 +4,7 @@ img_extIsRegExp=false
img_extensions=.eps .jpg .jpeg .png .pdf .ps .fig .gif
kileprversion=2
kileversion=2.1.3
-lastDocument=summary-20170409.tex
+lastDocument=summary-20090212.tex
masterDocument=
name=Gentoo Council Decicisions Index
pkg_extIsRegExp=false
@@ -1190,20 +1190,20 @@ order=-1
[item:decisions.bux]
archive=true
-column=24
+column=15
encoding=UTF-8
highlight=None
-line=117
+line=49
mode=
open=true
order=1
[item:decisions.ded]
archive=true
-column=13
+column=14
encoding=UTF-8
highlight=None
-line=49
+line=43
mode=
open=true
order=2
@@ -1230,10 +1230,10 @@ order=0
[item:documents.tex]
archive=true
-column=0
+column=28
encoding=UTF-8
highlight=LaTeX
-line=228
+line=229
mode=LaTeX
open=true
order=4
@@ -1690,10 +1690,10 @@ order=-1
[item:summary-20090122.tex]
archive=true
-column=24
+column=19
encoding=UTF-8
highlight=LaTeX
-line=23
+line=18
mode=LaTeX
open=false
order=5
@@ -1703,10 +1703,10 @@ archive=true
column=0
encoding=UTF-8
highlight=LaTeX
-line=0
+line=90
mode=LaTeX
-open=false
-order=-1
+open=true
+order=5
[item:summary-20090226.tex]
archive=true
@@ -2845,20 +2845,20 @@ encoding=UTF-8
highlight=LaTeX
line=0
mode=LaTeX
-open=true
+open=false
order=5
[view-settings,view=0,item:decisions.bux]
-CursorColumn=24
-CursorLine=117
+CursorColumn=15
+CursorLine=49
JumpList=
-ViMarks=.,117,23,[,116,0,],117,23
+ViMarks=.,49,14,[,48,0,],49,14
[view-settings,view=0,item:decisions.ded]
-CursorColumn=13
-CursorLine=49
+CursorColumn=14
+CursorLine=43
JumpList=
-ViMarks=.,49,0,[,47,0,],49,12
+ViMarks=.,43,14,[,43,14,],43,14
[view-settings,view=0,item:decisions.gld]
CursorColumn=22
@@ -2873,10 +2873,10 @@ JumpList=
ViMarks=.,471,24,[,471,25,],471,24
[view-settings,view=0,item:documents.tex]
-CursorColumn=0
-CursorLine=228
+CursorColumn=28
+CursorLine=229
JumpList=
-ViMarks=.,228,0,[,228,0,],228,0
+ViMarks=.,229,27,[,229,22,],229,27
[view-settings,view=0,item:summary-20050915.tex]
CursorColumn=0
@@ -3149,16 +3149,16 @@ JumpList=
ViMarks=.,52,43,[,52,43,],52,43
[view-settings,view=0,item:summary-20090122.tex]
-CursorColumn=24
-CursorLine=23
+CursorColumn=19
+CursorLine=18
JumpList=
-ViMarks=.,14,64,[,14,44,],14,64
+ViMarks=.,18,18,[,18,0,],18,18
[view-settings,view=0,item:summary-20090212.tex]
CursorColumn=0
-CursorLine=0
+CursorLine=90
JumpList=
-ViMarks=
+ViMarks=.,88,0,[,88,0,],88,0
[view-settings,view=0,item:summary-20090226.tex]
CursorColumn=0
diff --git a/decisions/decisions.mlf b/decisions/decisions.mlf
index 6c76aaf..4b0d68c 100644
--- a/decisions/decisions.mlf
+++ b/decisions/decisions.mlf
@@ -62,6 +62,8 @@ Michał Górny
Ulrich Mueller
21de1bcb87913938d804afa39f8f1d35:gentoo-dev
Ciaran McCreesh
+221d6a37687a1512034bb2757c560d0a:gentoo-dev
+Mike Frysinger
2342bd1cad57e432a319c55e3ef7e6df:gentoo-dev
Michał Górny
2406f61ebe526f4f3d9e23227aa1b96b:gentoo-dev
diff --git a/decisions/decisions.mls b/decisions/decisions.mls
index 9f78c42..5f22b2b 100644
--- a/decisions/decisions.mls
+++ b/decisions/decisions.mls
@@ -62,6 +62,8 @@ Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2015-10-11
[gentoo-pms] Re: [gentoo-dev] [RFC] Shall econf append its arguments to end of ./configure invocation?
21de1bcb87913938d804afa39f8f1d35:gentoo-dev
[gentoo-dev] Remaining PMS todo list etc
+221d6a37687a1512034bb2757c560d0a:gentoo-dev
+[gentoo-dev] Monthly Gentoo Council Reminder for February
2342bd1cad57e432a319c55e3ef7e6df:gentoo-dev
[gentoo-dev] RFC: an eclass to handle optional runtime depends
2406f61ebe526f4f3d9e23227aa1b96b:gentoo-dev
diff --git a/decisions/decisions.mlt b/decisions/decisions.mlt
index 29e88ac..f434115 100644
--- a/decisions/decisions.mlt
+++ b/decisions/decisions.mlt
@@ -62,6 +62,8 @@ Sun, 04 Oct 2015 11:14:08
Tue, 30 Apr 2013 17:04:05
21de1bcb87913938d804afa39f8f1d35:gentoo-dev
Wed, 19 Mar 2008 18:27:31
+221d6a37687a1512034bb2757c560d0a:gentoo-dev
+Sun, 01 Feb 2009 10:30:08
2342bd1cad57e432a319c55e3ef7e6df:gentoo-dev
Sun, 31 Jul 2011 15:26:56
2406f61ebe526f4f3d9e23227aa1b96b:gentoo-dev
diff --git a/decisions/documents.tex b/decisions/documents.tex
index b35d975..cc8301b 100644
--- a/decisions/documents.tex
+++ b/decisions/documents.tex
@@ -226,3 +226,191 @@ rest of the team to forward on for council approval.
\chapter{Stabilization}
+
+\chapter{PMS, EAPIs, GLEPs, and similar}
+
+\section{Live Ebuild as template proposal}
+\label{2000-02-luzero-live}
+Source: \url{http://dev.gentoo.org/~lu_zero/glep/liveebuild.rst}, file is dated
+11 March 2009
+\index{GLEP!54}
+\index{developer!lu_zero}
+\vspace*{1cm}
+
+{\small \begin{verbatim}
+:GLEP: XXX
+:Title: Live Ebuild as Template
+:Version: $Revision: $
+:Last-Modified: $Date: $
+:Author: Luca Barbato <lu_zero@gentoo.org>,
+:Status: Draft
+:Type: Standards Track
+:Content-Type: text/x-rst
+:Created: 12 Jun 2008
+
+Credits
+=======
+
+Thanks to Gianni Ceccarelli for the early feedback and markup help, Zack Medico
+for pointing some issues and suggesting solutions (and pushing me to complete
+it), Thomas Anderson for the help.
+
+Abstract
+========
+
+This glep provides a mechanism to allow traceable installation from
+live source repositories (e.g. ``svn``, ``bzr``, ``git``) using
+ebuilds.
+
+Motivation
+==========
+
+Sometimes upstream may not provide releases often enough to satisfy certain
+needs, either because there isn't a release schedule or the scheduled release
+is too far to address certain issues or provide certain features in a timely
+manner.
+
+In order to provide such fixes or features the main solutions had been either
+backport them in form of patches or provide snapshots from the development
+tree if the number of changes is too high.
+
+Sometimes is needed to update the snapshots often enough that would be simpler
+directly using the live sources.
+
+Current situation (``-9999 ebuilds``)
+-----------------------------------
+
+Right now the are some eclasses that on unpack phase fetch the sources from
+the upstream server, prepare them and then the usual ebuild process follows.
+
+In order to make an ebuild using those eclasses be valued as the highest
+possible, the simplest solution had been give it a version "high enough",
+commonly ``9999``.
+That makes simple track a single live branch per package.
+
+The same reasoning could be done with any version component in order to try
+to track different branches:
+- to track what will be the next ``1.5`` version, a version like ``1.4.9999``
+ or 1.5_pre9999 could be used.
+- to track all the improvements happening on the 1.5 branch somebody could use
+ a version like 1.5_p9999 or 1.5.9999 again.
+
+9999 is just an arbitrary big number.
+
+Shortcomings
+------------
+
+There are many obvious and non obvious shortcomings in this situations:
+- you have to hand produce "high enough" version values and be sure they do
+ not clash (e.g. 2.3_pre9999 live ebuild being shadowed by 2.3_pre20050201
+ snapshot).
+- you cannot track what did you install since you don't have a precise
+ information about it, emerge logs will just provide you the build date.
+- you cannot do exact reemerges and that may break revdep-rebuild
+- the package manager isn't aware of the "liveness" condition.
+- in order to refresh/update the installed package automatically you need
+ either to rely on script or on sets hand produced or heuristically defined
+ (e.g "all ebuilds that inherit eclass svn go in svn set").
+- since you fetch on unpack phase you cannot use emerge --fetch consistently.
+
+
+This document aims to address the above shortcomings.
+
+Use Cases
+=========
+
+Those are the following use case considered::
+
+ * track the tip of the main branch
+ * track specific version branches
+ * track multiple topic branches
+ *
+
+
+Backwards Compatibility
+=======================
+
+This is an expansion to [GLEP54]_.
+
+
+Live Template
+=============
+
+Structure
+---------
+
+Any numeric version component could be substituted with the keyword ``live``.
+The keyword must be present at most one time::
+
+ ``cat/pkg-live``
+ ``cat/pkg-1.live``
+ ``cat/pkg-1.2.live``
+ ``cat/pkg-1.2.3_prelive``
+ ``cat/pkg-1.2.2_plive``
+
+It's advised not to chain suffixes beside ``-r`` after the live keyword
+even if is possible (e.g. ``cat/pkg-1.2.live_pre``)
+
+Resolution and Version Comparison
+---------------------------------
+
+At resolution the live keyword is substituted with a timestamp in the form of
+iso date (``YYYYMMDDhhmm``) and the version comparison follows the normal
+version comparison rules.
+
+Generation
+----------
+
+[Details about generating a normal ebuild out of template]
+
+Informations shown on pretend
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The live template is always resolved to a snapshot value, portage should mark
+both template and rendered templates to notify the user.
+
+live template yet to be rendered could get a specific letter "L" in order to
+mark it or it could be shown as is.
+Rendered templates will shown with the version with ``live`` replaced with the
+iso date and the informations about the branch and revision name will be shown
+on verbose in a fashion similar to what is used for useflags.
+
+Additional Phase
+~~~~~~~~~~~~~~~~
+
+[Reference about ``src_fetch`` bugXXXX_]
+
+Revision information embedding
+------------------------------
+
+In order to properly allow re-emerge, it's required that additional informations
+will be stored and exposed to portage.
+
+Eclass Support
+~~~~~~~~~~~~~~
+
+Live templates will use a standardized form of eclass interface to expose the
+revision information to the ebuild and the package manager.
+
+Every ebuild will expose the following variables:
+
+``LIVE_URI``
+``LIVE_BRANCH``
+``LIVE_REVISION``
+
+
+References
+==========
+
+.. [GLEP54] scm package version suffix
+ (http://glep.gentoo.org/glep-0054.html)
+.. [bugXXXX] src_fetch rfe (http://bugs.gentoo.org/XXXX)
+
+
+
+Copyright
+=========
+
+This document has been placed in the public domain.
+
+\end{verbatim}}
diff --git a/decisions/summary-20090122.tex b/decisions/summary-20090122.tex
index 54b3062..c855ebf 100644
--- a/decisions/summary-20090122.tex
+++ b/decisions/summary-20090122.tex
@@ -16,6 +16,7 @@ there was not much momentum for any changes. No action was taken.
\agendaitem{Are prep* functions are part of the public Portage API?}
+\index{prepalldocs}
References: \bug{250077}
diff --git a/decisions/summary-20090212.tex b/decisions/summary-20090212.tex
index 1868c13..63f00f7 100644
--- a/decisions/summary-20090212.tex
+++ b/decisions/summary-20090212.tex
@@ -1,64 +1,70 @@
\summary{2009}{2}{12}
+Agenda call: \agoref{gentoo-dev}{221d6a37687a1512034bb2757c560d0a}
+
+Agenda announcement: ?
+
+
+
\agendaitem{Should the council have a dedicated secretary?}
\index{council!secretary}
- Previously dberkholz fulfilled this roll, but he became busy.
- Because fulfilling the secretary duties can distract from the
- meeting, a dedicated, non-council member secretary is ideal.
+Previously \dev{dberkholz} fulfilled this role, but he became busy. Because
+fulfilling the secretary duties can distract from the meeting, a dedicated,
+non-council member secretary is ideal.
+
+Conclusion: \dev{tanderson} volunteered and is the new secretary. Logs and
+summary are to be posted on the -council mailing list. If no objections to them
+are raised within one day, they are posted to the council page and the lists.
- Conclusion:
- tanderson is the new secretary. Logs and summary are to be
- posted on the -council mailing list. If no objections to it
- are raised in 1 day, it is posted to the council page and lists.
\agendaitem{Council Elections}
\index{council!election}
- Should there be staggered elections every 6 months where half the
- council members stand for reelection?
+Should there be staggered elections every 6 months where half the council
+members stand for reelection?
- Conclusion:
- Leave as-is, elections every 6 months is too cumbersome. Full elections
- will be held once a year.
+Conclusion: Leave things as they are; elections every 6 months is too
+cumbersome. Full elections will be held once a year.
- What happens if there aren't enough candidates nominated to fill all
- the council seats?
+What happens if there aren't enough candidates nominated to fill all the
+council seats?
- Conclusion:
- If the pseudo-candidate '_reopen_nominations' appears in 7th place
- or higher those candidates that rank above '_reopen_nominations'
- will be the current council. A second period of nominations will
- be opened for the remaining council seats. No third period of
- nominations will be opened in the event '_repoen_nominations'
- ranks higher than the candidates necessary to fill the council.
+Conclusion: If the pseudo-candidate '_reopen_nominations' appears in 7th place
+or higher those candidates that rank above '_reopen_nominations' will be the
+current council. A second period of nominations will be opened for the remaining
+council seats. No third period of nominations will be opened in the event
+'_reopen_nominations' ranks higher than the candidates necessary to fill the
+council.
\agendaitem{Prepalldocs}
\index{prepalldocs}\index{EAPI!0}\index{EAPI!1}\index{EAPI!2}
- Should 'prepalldocs' be allowed in current EAPIs?
+Reference: \bug{250077}
+
+Should 'prepalldocs' be allowed in current EAPIs?
+
+Conclusion: Prepalldocs is banned in current EAPIs (0, 1, 2). It should be
+removed from ebuilds. \dev{betelgeuse} will make QA checks for repoman.
+
- Conclusion:
- Prepalldocs is banned in current EAPIs(0,1,2). It should be
- removed from ebuilds. Petteri Räty(Betelgeuse) will make QA
- checks for repoman.
\agendaitem{BASH version allowed in the tree}
\index{bash!features in ebuilds}\index{PMS}
- PMS states that ebuilds can only rely on BASH 3.0 features. However,
- some code in gentoo-x86 uses BASH 3.1 features('+=' being the most
- notable) and so is not in conformance with PMS. It was suggested that
- BASH versions newer than 3.0 be allowed in a future EAPI. Ciaran
- Mccreesh, however, commented that this would require GLEP 55 being
- accepted so that a package manager would not have to source the ebuild
- before knowing what BASH version it requires.
+PMS states that ebuilds can only rely on BASH 3.0 features. However, some code
+in gentoo-x86 uses BASH 3.1 features('+=' being the most notable) and so is not
+in conformance with PMS. It was suggested that BASH versions newer than 3.0 be
+allowed in a future EAPI. \dev{ciaranm}, however, commented that this would
+require \glep{55} being accepted so that a package manager would not have to
+source the ebuild before knowing what BASH version it requires.\footnote{This
+discussion cannot be found in the meeting log. However, it is referenced in the
+meeting log during the ``open bugs'' discussion.}
- Conclusion:
- No decision. Doug(Cardoe) will follow this up with
- Tiziano(dev-zero) as a backup.
+Conclusion: No decision. \dev{cardoe} will follow this up with \dev{dev-zero}
+as a backup.
\agendaitem{Open Bugs}
@@ -66,29 +72,20 @@
\begin{itemize}
\item
\bug{234711}:
- GLEP 54 solves two problems, version ordering and periodic reinstall
- of live packages. The Live Template proposal
-\url{http://dev.gentoo.org/~lu_zero/glep/liveebuild.rst} overlaps in that it
-also
- allows for periodic reinstall of live packages. Luca(lu_zero)
- maintains that Live Template provides proper version ordering, while
- Ciaran(ciaranm) maintains that it does not.
-
- Conclusion:
- No decision. The council cracked the whip on Luca(lu_zero) and
- he's going to handle the issue.
+ \glep{54} solves two problems, version ordering\footnote{This was actually a
+ matter of debate during the meeting.} and periodic reinstall of live packages.
+ The Live Template proposal
+ http://dev.gentoo.org/~lu_zero/glep/liveebuild.rst\footnote{See
+ \ref{2000-02-luzero-live} for the text.} overlaps in that it also allows for
+ periodic reinstall of live packages. \dev{lu_zero} maintains that Live Template
+ provides proper version ordering, while \dev{ciaranm} maintains that it does
+ not.\\
+ Conclusion: No decision. The council cracked the whip on \dev{lu_zero} and
+ he is going to handle the issue.
\item
- GLEP 55(.ebuild-\$eapi ebuild suffix)
-
- Should .ebuild-\$eapi be approved? This ties in with "BASH version
- allowed in the tree" issue mentioned above.
-
- Conclusion:
- No decision. Tiziano(dev-zero) will be handling this bug.
+ \glep{55}: Should .ebuild-\$eapi be approved? This ties in with "BASH version
+ allowed in the tree" issue mentioned above.\\
+ Conclusion: No decision. \dev{dev-zero} will be handling this bug.
+\end{itemize}
- \item
- Code of Conduct
- Conclusion:
- No decision. Donnie(dberkholz) will be handling this bug.
-\end{itemize}