1 |
* Alan McKinnon <alan.mckinnon@×××××.com> schrieb: |
2 |
|
3 |
> My biggest beef by far when packaging apps is automagic dependencies. |
4 |
> |
5 |
> e17 is full of them - if package A is present, the app will configure itself |
6 |
> to use it. Usually you cannot switch this kind of thing off even if you have |
7 |
> valid reasons to do so. |
8 |
|
9 |
That's one of the reasons I'm building everything by a sysroot'ed |
10 |
crosscompiler (when not using Gentoo ;-)). This way these things |
11 |
(normally) can't happen. |
12 |
|
13 |
> I want explicit --enable-<package> features in the ./configure step for |
14 |
> everything that might be optional. Because I often do have that lib on my |
15 |
> system and the app's usage of it is buggy, so I should be able to disable that |
16 |
> support. |
17 |
|
18 |
Can you live with the current formulation ? |
19 |
http://www.metux.de/index.php/de/component/content/article/57.html |
20 |
|
21 |
(see and of the text) |
22 |
|
23 |
|
24 |
cu |
25 |
-- |
26 |
---------------------------------------------------------------------- |
27 |
Enrico Weigelt, metux IT service -- http://www.metux.de/ |
28 |
|
29 |
phone: +49 36207 519931 email: weigelt@×××××.de |
30 |
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 |
31 |
---------------------------------------------------------------------- |
32 |
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme |
33 |
---------------------------------------------------------------------- |