Ciaran McCreesh wrote:
* What generation looks like.
Mostly implementation detail? Somebody seems to have ideas there and I like to heard ideas from others as well.
* How to select which ebuilds to trigger generation for.
I'm fond of sets and I'd extend maint to be feeded to sets other than world and all.
* When specifically to trigger generation.
User decision or triggered by sync depending on a FEATURE.
* Whether generation failure is possible, and what happens if it is.
I could think easily that such thing could happen (no network is a possibility)
* What to do when generated information is required but not available.
Consider the ebuild corrupted or do not generate it.
* The security implications of the previous point.
None?
* What the impact upon upstream servers is, if any.
Shared with glep 54
* How generation fits in with users doing system updates.
Orthogonal
* How generation fits in with the highly differing frequencies of upstream updates.
Being user driven isn't an issue at all.
* How generation can be made to fit in without changes to the version spec, whilst still 'making sense' and doing the right thing.
Discussion going on in this thread, so far Coldwind did quite well to pointing actual cases present in portage already, discussion on them should help sorting out issues.
Using live sources is a security and stability concern by itself and by accepting that you are at the very end of the bleeding edge you acknowledge that you are experimenting.
lu -- Luca Barbato Gentoo Council Member Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- gentoo-dev@lists.gentoo.org mailing list
