Gentoo Archives: gentoo-dev

From: Brian Harring <ferringb@×××××.com>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] glep52 issues
Date: Sun, 19 Nov 2006 02:48:44
Message-Id: 20061119024454.GD10696@seldon
1 Since interactivity (eula or otherwise) is again being brought up,
2 read through glep52 a bit, found some issues-
4 1) Specification doesn't actually lay out the mechanism for filtering.
5 User tweaks what to block interactive ebuilds?
7 2) What ebuild phases are allowed to be interactive? Scenario being,
8 some 'smart' ebuild dev does something interactive in pre_rm, user
9 installs the ebuild, later on disables interactivity; the reference
10 patch only does checks against portdb, doesn't check against vardb;
11 meaning that it'll miss that pre_rm requires interactivity.
13 That's also ignoring pre_inst for binpkgs that may require
14 interactivity... hence the question of what phases are allowed?
16 Personally, inclined to keep it as minimal as possible- for parallel
17 execution of builds, the interactive build *must* be in the
18 foreground, meaning you can't have two interactive ebuilds building in
19 parallel (can, but can easily wind up with one of them stalled out
20 waiting on input).
22 Off the top of my head, would assume that src_unpack and pkg_setup are
23 enough; that said, could see people wanting to abuse interactivity for
24 src_test (xdg-utils comes to mind), and/or src_compile (kernel or
25 uclinux configuration).
27 So... needs narrowing down, question being "narrowed down to what
28 phases?"
30 ~harring