1 |
Hello, all. |
2 |
|
3 |
The last discussion on new solutions optional runtime depends lead to no |
4 |
agreement. Thus, I'd like to propose a solution extending the usability |
5 |
of current methods of handling them. |
6 |
|
7 |
My idea is to create an eclass which would take a optional dependency |
8 |
list (e.g. through some kind of SDEPEND variable or so [being a bash |
9 |
array!]) and print it out to user in pkg_postinst(). |
10 |
|
11 |
The eclass could also denote whether the particular package is |
12 |
installed like I do in sys-apps/systemd [1]. |
13 |
|
14 |
But first, I'd like to ask interested devs: how many packages need more |
15 |
than a single dep for a single optional feature? How would like such a |
16 |
deps to be printed as? |
17 |
|
18 |
I thought about something like: |
19 |
|
20 |
SDEPEND=( |
21 |
app-foo/bar "blah blah blah blah" |
22 |
app-bar/foo "fooh fooh fooh fooh" |
23 |
) |
24 |
|
25 |
Though not sure how to handle support for many-to-one deps. |
26 |
|
27 |
[1]:http://git.overlays.gentoo.org/gitweb/?p=dev/mgorny.git;a=blob;f=sys-apps/systemd/systemd-9999.ebuild;h=2703d8621874c3a9f961d1e0a764f88c56cdcd30;hb=HEAD#l126 |
28 |
|
29 |
-- |
30 |
Best regards, |
31 |
Michał Górny |