Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
May 12, 2007, 12:15:04 AM (17 years ago)
- Author:
-
rlaager
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v6
|
v7
|
|
8 | 8 | As a convenience, an extra, we provide binary installers where we have |
9 | 9 | developers able and willing to do so. Thus we have developers with a |
10 | | significant number of redhat and fedora machines or chroot environments. |
11 | | These developers create the various rpm packages you see. |
| 10 | significant number of RedHat and Fedora machines or chroot environments. |
| 11 | These developers create the various RPM packages you see. |
12 | 12 | |
13 | 13 | |
14 | | While we have a few developers using debian systems, the debian package |
| 14 | While we have a few developers using Debian systems, the Debian package |
15 | 15 | maintainers have historically worked closely with us and provided timely |
16 | 16 | updates to the official packages. There has been no need on our part to |
17 | | create packages for debian unstable, and no desire on our part to try to |
18 | | create backport packages to debian testing or stable. |
19 | | |
| 17 | create packages for Debian unstable, and no desire on our part to try to |
| 18 | create backport packages to Debian testing or stable. The situation with Ubuntu is the same. |
20 | 19 | |
21 | | We have no developers using Slack, and furthermore, several of us |
22 | | actively dislike that distribution for its history of broken installs, |
23 | | as well as for its non-existent package management. You cannot create |
24 | | true packages for Slack. |
25 | | |
| 20 | We have no developers using Slackware, and we do ''not'' support it, due |
| 21 | to a history of problems which are caused or made unnecessarily difficult to solve |
| 22 | by the fact that its package system does not support automatic dependency resolution. |
| 23 | We also recommend that users do not attempt to compile Pidgin from source on |
| 24 | Slackware, but instead use the packages provided by the Slackware team. If you |
| 25 | insist on trying this out yourself, the only advice we can give you is to ask |
| 26 | for help in ##slackware on irc.freenode.org, or on the Slackware mailing lists. |
26 | 27 | |
27 | 28 | We have no developers using arch, SuSE, or any other distribution. |
… |
… |
|
31 | 32 | |
32 | 33 | |
33 | | While the same holds true of MacOSX, we do not provide OSX packages, preferring to point users to Adiumx, because Pidgin, as an X11 application, will never integrate into an OSX user's environment as cleanly as a native program can. Ideally the Pidgwin version will be replaced by a more native Windows UI at some point, and we will be able to stop producing the Windows installers as well. |
| 34 | While the same holds true of OS X, we do not provide OS X packages, preferring to point users to Adium, because Pidgin, as an X11 application, will never integrate into an OS X user's environment as cleanly as a native program can. Ideally, the Pidgwin version will be replaced by a more native Windows UI at some point, and we will be able to stop producing the Windows installers as well. |
34 | 35 | |
35 | 36 | |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!