Rev 3 | Only display areas with differences | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 3 | Rev 27 | ||
---|---|---|---|
1 | liboop for Debian |
1 | liboop for Debian |
2 | ----------------- |
2 | ----------------- |
3 | 3 | ||
4 | I've chosen at this stage not to package the adapter libraries separately, |
4 | I've chosen at this stage not to package the adapter libraries separately, |
5 | since the package only weighs in at just over 500k when unpacked. If anyone |
5 | since the package only weighs in at just over 500k when unpacked. If anyone |
6 | would rather that these were all in separate packages, please let me know |
6 | would rather that these were all in separate packages, please let me know |
7 | and I'll think again about doing this ... At the moment, the package _DOES |
7 | and I'll think again about doing this ... At the moment, the package _DOES |
8 | NOT DEPEND_ on any of the libraries required to use the adapter libraries, |
8 | NOT DEPEND_ on any of the libraries required to use the adapter libraries, |
9 | so if your package uses one of the adapter libraries, you _must_ depend on |
9 | so if your package uses one of the adapter libraries, you _must_ depend on |
10 | the appropriate library (ie. if you link with liboop-tcl, you must also |
10 | the appropriate library (ie. if you link with liboop-tcl, you must also |
11 | depend on tcl8.3 ...). The same goes for Build-Depends. |
11 | depend on tcl8.3 ...). The same goes for Build-Depends. |
12 | 12 | ||
13 | My reasoning for packaging liboop in this way is to avoid having to install |
13 | My reasoning for packaging liboop in this way is to avoid having to install |
14 | excessive numbers of large-ish packages (tcl for instance) just to install |
14 | excessive numbers of large-ish packages (tcl for instance) just to install |
15 | your program that depends on liboop. |
15 | your program that depends on liboop. |
16 | 16 | ||
17 | I haven't compiled in the libwww adapter support - this is primarily because |
17 | I haven't compiled in the libwww adapter support - this is primarily because |
18 | the current libwww0 package in Debian doesn't include libwwwxml, because when |
18 | the current libwww0 package in Debian doesn't include libwwwxml, because when |
19 | this library is compiled there is a name clash (libwww also includes |
19 | this library is compiled there is a name clash (libwww also includes |
20 | libxmltok and libxmlparse, which are in the libxmltok1 package). It's |
20 | libxmltok and libxmlparse, which are in the libxmltok1 package). It's |
21 | difficult to compile liboop support for libwww libraries excluding libwwwxml, |
21 | difficult to compile liboop support for libwww libraries excluding libwwwxml, |
22 | as the configure script simply links liboop-www with all of the libwww |
22 | as the configure script simply links liboop-www with all of the libwww |
23 | libraries, including libwwwxml. I'm working on a solution to this with the |
23 | libraries, including libwwwxml. I'm working on a solution to this with the |
24 | libwww maintainer. In the meantime, liboop Build-Conflicts: libwww-dev. If |
24 | libwww maintainer. In the meantime, liboop Build-Conflicts: libwww-dev. If |
25 | you need this support urgently, feel free to contact me and I'll hurry up |
25 | you need this support urgently, feel free to contact me and I'll hurry up |
26 | my work on this (no real urgency at the moment, however ...) |
26 | my work on this (no real urgency at the moment, however ...) |
27 | 27 | ||
28 | -- Timshel Knoll <timshel@debian.org> Tue, 5 Mar 2002 15:41:41 +1100 |
28 | -- Timshel Knoll <timshel@debian.org> Tue, 5 Mar 2002 15:41:41 +1100 |