Rev 126 | Details | Compare with Previous | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 4 | magnus | 1 | Missing modules |
| 2 | --------------- |
||
| 3 | |||
| 4 | The following modules are not included in the Debian Pike packages for |
||
| 5 | various reasons, even if they are included in the module reference |
||
| 6 | (pike7.6-reference): |
||
| 7 | |||
| 8 | - DVB: Doesn't work with Linux 2.6 (and certainly not with other OSes). |
||
| 9 | - _Ffmpeg: formerly missing from Debian due to patent issues. Might be |
||
| 10 | included in the next release. |
||
| 11 | - Gnome, GTK, GDK: Uses obsolete GTK version (1.2). |
||
| 11 | magnus | 12 | - Math.Transforms.FFT: Few use cases in Pike, pulls in unnecessary |
| 13 | dependencies. |
||
| 14 | - Mird: Old, unmaintained, largely unknown library. |
||
| 4 | magnus | 15 | - Msql: Obsolete, proprietary DBM. |
| 16 | - PDF: Uses unmaintained libraries unavailable in Debian. |
||
| 17 | - Ssleay: Obsolete. |
||
| 18 | - Oracle: Proprietary DBM (so far ...). |
||
| 11 | magnus | 19 | - Java: Links with the JVM library in a non-policy compliant |
| 20 | way. Work needed. |
||
| 4 | magnus | 21 | - Image.TTF: Uses obsolete library (freetype1). |
| 22 | |||
| 2 | magnus | 23 | Places to visit |
| 24 | --------------- |
||
| 25 | - http://pike.ida.liu.se/ - the main Pike site |
||
| 26 | - http://community.roxen.com - community site for users of the |
||
| 27 | Roxen webserver and the Pike bugs database, information etc. |
||
| 28 | - http://caudium.net/ - website of the Caudium WebServer which is |
||
| 29 | written in Pike |
||
| 30 | - http://www.roxen.com/ - website of the Roxen IS, the company which |
||
| 31 | for a long time developed and maintained Pike as well as the Roxen |
||
| 32 | WebServer mentioned above. |
||
| 33 | |||
| 34 | Notes for developers |
||
| 35 | -------------------- |
||
| 36 | |||
| 37 | The postinst script created a few directories in /usr/local which you can |
||
| 38 | use for your modules/include files. Once created by the postinst script |
||
| 39 | they will never be touched by any pike package again. The directories |
||
| 40 | are: |
||
| 41 | |||
| 42 | /usr/local/include/pike |
||
| 43 | /usr/local/include/pike7.6 |
||
| 44 | |||
| 45 | /usr/local/lib/pike/site_pike |
||
| 46 | /usr/local/lib/pike7.6/site_pike |
||
| 47 | |||
| 48 | /usr/local/share/pike/site_pike |
||
| 49 | /usr/local/share/pike7.6/site_pike |
||
| 50 | |||
| 11 | magnus | 51 | Note: I have come to the conclusion that this structure isn't awfully |
| 52 | well though through. It is likely to change, but probably not until |
||
| 53 | Pike 7.8. What's missing is a working infrastructure for building and |
||
| 54 | installing third-pary modules and applications so that they won't have |
||
| 55 | to be rebuilt for each new Pike revision, similarly to Perl and/or |
||
| 56 | Python. Stay tuned. |
||
| 57 | |||
| 2 | magnus | 58 | ---- |
| 11 | magnus | 59 | $Id: README.Debian 11 2007-12-21 08:45:48Z magnus $ |
| 4 | magnus | 60 | |
| 11 | magnus | 61 | -- Magnus Holmgren <magnus@kibibyte.se>, Fri, 21 Dec 2007 09:43:18 +0100 |