1 |
On 14:38 Tue 28 Jun , Peter Volkov wrote: |
2 |
> 1. add a use flag to control runtime dependency |
3 |
> 2. add elog message into pkg_postinst to notify users that some |
4 |
> features depend on installing package A, B, etc. |
5 |
|
6 |
I've got a suggestion that builds a little bit on what both you and |
7 |
Ciaran have said. |
8 |
|
9 |
The UI could probably be clearer if we added a new dependency type like |
10 |
SDEPEND (suggested deps) with USE flags for different features. That |
11 |
would enable portage to show things in a special way if it knew about |
12 |
SDEPEND. Yet it wouldn't do anything weird that broke backwards |
13 |
compatibility or produced strange output from noncompliant PMs (like USE |
14 |
flag modifications). |
15 |
|
16 |
Then PMs would be free to implement their own logic for how to handle |
17 |
it. For Portage, I'd like to see a few cases: |
18 |
|
19 |
1) If a package is installed, assume it's desired, as Ciaran proposed. |
20 |
|
21 |
2) Add a way to determine whether to install all/none/groups of them, |
22 |
w/ configuration in /etc/portage/package.suggestions/. Probably CPV |
23 |
followed by the setting (all, none, specific groups, or specific |
24 |
CPVs). Add an option similar to --autounmask that would let Portage |
25 |
write to this file. |
26 |
|
27 |
3) Something like the --take argument and friends that Ciaran mentioned |
28 |
seems reasonable (perhaps --accept-suggestion, w/ a short option to |
29 |
save typing). |
30 |
|
31 |
Problems? Other thoughts? |
32 |
|
33 |
-- |
34 |
Thanks, |
35 |
Donnie |
36 |
|
37 |
Donnie Berkholz |
38 |
Sr. Developer, Gentoo Linux |
39 |
Blog: http://dberkholz.com |