Pidgin
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.

Changes between Version 12 and Version 13 of WhyPackagesExist


Ignore:
Timestamp:
May 13, 2007, 3:41:11 AM (17 years ago)
Author:
elb
Comment:

(typos again, whitespace) Fix ##slackware -- the ## is correct.

Legend:

Unmodified
Added
Removed
Modified

  • WhyPackagesExist

    v12 v13  
    44
    55                                                                                                                                                                                                   
    6 As a convenience, an extra, we provide binary installers where we have developers able and willing to do so.  We have developers with a significant number of Red Hat and Fedora machines or chroot environments, thus we provde various RPM packages.                                                                                                                             
     6As a convenience, an extra, we provide binary installers where we have developers able and willing to do so.  We have developers with a significant number of Red Hat and Fedora machines or chroot environments, thus we provide various RPM packages.                                                                                                                             
    77                                                                                                                                                                                                   
    88
    … …  
    1111
    1212We have no developers using Slackware, and we do ''not'' support it, due to a history of problems which are caused or made unnecessarily difficult to solve by the fact that its package system does not support automatic dependency resolution.
    13 We also recommend that users do not attempt to compile Pidgin from source on Slackware, but instead use the packages provided by the Slackware team. If you insist on trying this out yourself, the only advice we can give you is to ask for help in #slackware on irc.freenode.org, or on the Slackware mailing lists.
     13We also recommend that users do not attempt to compile Pidgin from source on Slackware, but instead use the packages provided by the Slackware team. If you insist on trying this out yourself, the only advice we can give you is to ask for help in ##slackware on irc.freenode.org, or on the Slackware mailing lists.
    1414
    1515
    … …  
    2626                                                                                                                                                                                                   
    2727
    28 As I said, the fact that we provide binary installers at all should be viewed rather as an extra, as the primary source for packages should always be your distro.  When you get packages for your distro, you have a level of assurance that this package will not break unrelated services or programs that cannot exist when getting 3rd party packages from us,                                    or from any other source.  Additionally, the distros often apply patches                                              to Pidgin, and while sometimes these patches cause problems, they also                                                        often fix bugs that were discovered after the release.
     28As I said, the fact that we provide binary installers at all should be viewed rather as an extra, as the primary source for packages should always be your distro.  When you get packages for your distro, you have a level of assurance that this package will not break unrelated services or programs that cannot exist when getting 3rd party packages from us, or from any other source.  Additionally, the distros often apply patches to Pidgin, and while sometimes these patches cause problems, they also often fix bugs that were discovered after the release.
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!