[gentoo-council] Initial Council summary for meeting on 04/22

[gentoo-council] Initial Council summary for meeting on 04/22

[Thomas Anderson]

[-- Attachment #1.1: Type: text/plain, Size: 355 bytes --]

Hi,

    Sorry this is so late, RL ate my time for the past week or so. But
    finals are over, so I'm good now. Enjoy your latest edition of the
    bi-weekly gentoo newsletter(j/k :) ).

Regards,
Thomas

-- 
---------
Thomas Anderson
Gentoo Developer
/////////
Areas of responsibility:
AMD64, Secretary to the Gentoo Council
---------

[-- Attachment #1.2: councilsummary-20090422.txt --]
[-- Type: text/plain, Size: 3013 bytes --]

Roll Call:
===========
Betelgeuse: here
Cardoe: absent
dberkholz: here
dertobi123: here
dev-zero: here
leio: here
lu_zero: here 
tanderson(secretary): here

Topics:
===========

Technical Issues:

    - Portage changing behaviour without EAPI bumps:
        David Leverton(dleverton) requested that the council mandate that portage
        is not allowed to change behaviour that is specified in PMS, as has
        occurred a few times in the past.

        Conclusion:
            The council decided that if PMS-conflicting changes occur in
            package managers then the council can mandate that versions that
            conflict will be masked, excepting extenuating circumstances.

    - EAPI 3:
        EAPI 3's features have been finalized and its final approval is
        pending portage support for the most important features. Some features
        may be removed if they cannot be accomplished in a reasonable
        timeframe and are holding up the introduction of the critical
        features.

        - New utility functions: 'Doexample'/'Doexample'
            Some council members believed that adding these utility functions
            would complicate things for new ebuild authors while not providing
            any especially needed features.

            Conclusion:
                Voted to not be included in EAPI 3.

        - Ban || ( use? ( ... ) ... )
            Mart Raudsepp(leio) argued that banning such constructs is
            strictly a QA issue and shouldn't be covered by PMS, while others
            argued that there are no valid use cases for the construct and
            that you need appropriate rules to parse RDEPEND/DEPEND.

            Conclusion:
                It was decided that a repoman warning would be most
                appropriate for this case and that the topic of banning it in
                an EAPI can be revisited for EAPI 4.

        - Ban 'dohard'
            Currently dohard cannot be guaranteed to work across filesystems
            and few packages use it.

            Conclusion:
                Voted to be banned in EAPI 3.

        - New econf options,
          '--disable-dependency-tracking'/'--enable-fast-install'
            The addition of '--enable-fast-install' was opposed because it is
            already a libtool default and as such is useless. No arguments
            were made against '--disable-dependency-tracking'.

            Conclusion:
                '--disable-dependency-tracking' was voted in, while
                '--enable-fast-install' was voted out.

        - Add --if-compressed option to unpack().
            
            Conclusion:
                Voted to be not included in EAPI 3.

        - Slot Operator Dependencies(:= and :*)
            
            Conclusion:
                 Voted to be included in EAPI 3. Mart Raudsepp has remaining
                 queries about the final syntax.


[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]