特殊:Badtitle/NS100:Pidgin:修订间差异

来自Ubuntu中文
跳到导航跳到搜索
Wikibot留言 | 贡献
无编辑摘要
Wikibot留言 | 贡献
无编辑摘要
第10行: 第10行:
The recommended way to install Pidgin is through the official Ubuntu repositories. That way you'll get the supported version.
The recommended way to install Pidgin is through the official Ubuntu repositories. That way you'll get the supported version.
Installing through the repositories is pretty straightforward:
Installing through the repositories is pretty straightforward:
# Go to '''Applications''' -> '''Add/Remove...'''
<ol><li>Go to '''Applications''' -> '''Add/Remove...'''
2. Search for ''Pidgin'' and tick the box with ''Pidgin Internet Messenger''.
</li><li>Search for ''Pidgin'' and tick the box with ''Pidgin Internet Messenger''.
3. Press '''Apply Changes''' and, if asked, enter your password.
</li><li>Press '''Apply Changes''' and, if asked, enter your password.</li></ol>
 
For more info about how to install software from the repositories, see [[UbuntuHelp:InstallingSoftware|InstallingSoftware]].
For more info about how to install software from the repositories, see [[UbuntuHelp:InstallingSoftware|InstallingSoftware]].
== Install current release from official website ==
== Install current release from official website ==
第20行: 第21行:
==== Removing Gaim ====
==== Removing Gaim ====
Before you start, you have to make sure Gaim, the predecessor of Pidgin, is not already installed. This can be done following these instructions:
Before you start, you have to make sure Gaim, the predecessor of Pidgin, is not already installed. This can be done following these instructions:
# Go to '''System''' -> '''Administration''' -> '''Synaptic Package Manager'''
<ol><li>Go to '''System''' -> '''Administration''' -> '''Synaptic Package Manager'''
2. Enter the password for your user account and press OK
</li><li>Enter the password for your user account and press OK
3. Press 'Search', and enter ''gaim'' into the search field
</li><li>Press 'Search', and enter ''gaim'' into the search field
5. If the ''gaim'' package is selected, then deselect it  
</li><li>If the ''gaim'' package is selected, then deselect it
6. Press ''Apply''.
</li><li>Press ''Apply''.</li></ol>
 
==== Getting the necessary dependencies ====
==== Getting the necessary dependencies ====
Now, with a 'clean table', we can proceed. First, you need to install some libraries, which Pidgin will need in order to work:
Now, with a 'clean table', we can proceed. First, you need to install some libraries, which Pidgin will need in order to work:
# Go to '''Applications''' -> '''Accessories''' -> '''Terminal'''
<ol><li>Go to '''Applications''' -> '''Accessories''' -> '''Terminal'''
2. Type <pre><nowiki>sudo apt-get install libgtk2.0-dev libxml2-dev gettext libnss-dev libnspr-dev
</li><li>Type <pre><nowiki>sudo apt-get install libgtk2.0-dev libxml2-dev gettext libnss-dev libnspr-dev
</nowiki></pre> to get the proper dependencies.
</nowiki></pre> to get the proper dependencies.</li></ol>
 
===== Optional libraries for extra features =====
===== Optional libraries for extra features =====
* If you wish to include spell checking, add ''libgtkspell-dev'' to that list.
* If you wish to include spell checking, add ''libgtkspell-dev'' to that list.
第36行: 第39行:
=== Downloading and extracting Pidgin ===
=== Downloading and extracting Pidgin ===
Your system should now be prepared to handle Pidgin, so it's time to get the Pidgin source code. This is pretty straightforward:
Your system should now be prepared to handle Pidgin, so it's time to get the Pidgin source code. This is pretty straightforward:
# Download ''pidgin-2.1.1.tar.bz2'' from [http://www.pidgin.im/pidgin/download/source/]
<ol><li>Download ''pidgin-2.1.1.tar.bz2'' from [http://www.pidgin.im/pidgin/download/source/]
2. When downloaded, right-click on ''pidgin-2.1.1.tar.bz2'', which should be in your default Downloads-directory, and select «'''Extract Here'''»
</li><li>When downloaded, right-click on ''pidgin-2.1.1.tar.bz2'', which should be in your default Downloads-directory, and select «'''Extract Here'''»</li></ol>
 
=== Installation ===
=== Installation ===
Okay, so now you have all that you need, now it's all about compiling and installing:
Okay, so now you have all that you need, now it's all about compiling and installing:
# Go to '''Applications''' -> '''Accessories''' -> '''Terminal'''  
<ol><li>Go to '''Applications''' -> '''Accessories''' -> '''Terminal'''
2. Type <pre><nowiki>sudo apt-get install build-essential
</li><li>Type <pre><nowiki>sudo apt-get install build-essential
</nowiki></pre> to install a build environment (see [[UbuntuHelp:CompilingSoftware|CompilingSoftware]] for further information)
</nowiki></pre> to install a build environment (see [[UbuntuHelp:CompilingSoftware|CompilingSoftware]] for further information)
2. Change directory to the newly created ''pidgin-2.1.1'' directory using the '''cd''' command. (If you don't know how to use '''cd''', check [https://help.ubuntu.com/7.04/basic-commands/C/ar01s03.html#id2497610 "Commands"] in the [https://help.ubuntu.com/7.04 official Ubuntu documentation].)
</li><li>Change directory to the newly created ''pidgin-2.1.1'' directory using the '''cd''' command. (If you don't know how to use '''cd''', check [https://help.ubuntu.com/7.04/basic-commands/C/ar01s03.html#id2497610 "Commands"] in the [https://help.ubuntu.com/7.04 official Ubuntu documentation].)
3. When you've navigated the terminal to the ''pidgin-2.1.1'' directory, you have to type in the following in the Terminal: <pre><nowiki>./configure --enable-gnutls=yes
</li><li>When you've navigated the terminal to the ''pidgin-2.1.1'' directory, you have to type in the following in the Terminal: <pre><nowiki>./configure --enable-gnutls=yes
</nowiki></pre>
</nowiki></pre></li></ol>
 
(Note: The ''--enable-gnutls=yes'' flag means SSL support will be compiled in, which is required for the MSN and Google Talk protocols.)
(Note: The ''--enable-gnutls=yes'' flag means SSL support will be compiled in, which is required for the MSN and Google Talk protocols.)
4. Now Pidgin should be configured, and you should see a bunch of output on the screen. After it's finished configuring, it's time to create a makefile. In the same terminal, type: <pre><nowiki>make
<ol><li>Now Pidgin should be configured, and you should see a bunch of output on the screen. After it's finished configuring, it's time to create a makefile. In the same terminal, type: <pre><nowiki>make
</nowiki></pre>
</nowiki></pre>
5. Creating the makefile  is also going to take a little while, so grab a cup of coffee while you wait :)
</li><li>Creating the makefile  is also going to take a little while, so grab a cup of coffee while you wait :)
6. When the '''make''' command has finished, it's time to actually install Pidgin. This is done by typing: <pre><nowiki>make install
</li><li>When the '''make''' command has finished, it's time to actually install Pidgin. This is done by typing: <pre><nowiki>make install
</nowiki></pre>
</nowiki></pre>
7. When it's finished, then you should have Pidgin installed. Congratulations!
</li><li>When it's finished, then you should have Pidgin installed. Congratulations!</li></ol>
 
=== Clean up ===
=== Clean up ===
With Pidgin installed, you have the option of doing a little cleaning up of the files that were created and used doing installation, but aren't used anymore:
With Pidgin installed, you have the option of doing a little cleaning up of the files that were created and used doing installation, but aren't used anymore:
# While remaining in the same terminal, type in <pre><nowiki>make clean
<ol><li>While remaining in the same terminal, type in <pre><nowiki>make clean
</nowiki></pre>
</nowiki></pre>
2. When finished, type in: <pre><nowiki>make distclean
</li><li>When finished, type in: <pre><nowiki>make distclean
</nowiki></pre> to also remove the files that `./configure` created.
</nowiki></pre> to also remove the files that `./configure` created.</li></ol>
 
== Other info ==
== Other info ==
This section deals with other aspects of Pidgin than installing.  
This section deals with other aspects of Pidgin than installing.  
第65行: 第72行:
You can find all the currently reported bugs in the Pidgin bugtracker, which is located [http://developer.pidgin.im/wiki/OpenTickets here].
You can find all the currently reported bugs in the Pidgin bugtracker, which is located [http://developer.pidgin.im/wiki/OpenTickets here].
To report a bug, you need to do the following:
To report a bug, you need to do the following:
# Go to http://developer.pidgin.im
<ol><li>Go to http://developer.pidgin.im
2. Click "register" and pick a username and password
</li><li>Click "register" and pick a username and password
3. Back at http://developer.pidgin.im click "New Ticket"
</li><li>Back at http://developer.pidgin.im click "New Ticket"
4. Describe the bug, and mark what type it is. There are several types:
</li><li>Describe the bug, and mark what type it is. There are several types:</li></ol>
 
*'''defect''' are problems/bugs in Pidgin
*'''defect''' are problems/bugs in Pidgin
*'''enhancement''' is an idea for how to improve the functionality of Pidgin. This corresponds to the "Wishlist" priority on [[UbuntuHelp:Launchpad]]
*'''enhancement''' is an idea for how to improve the functionality of Pidgin. This corresponds to the "Wishlist" priority on [[UbuntuHelp:Launchpad]]
第75行: 第83行:
*'''task''' is for anything that doesn't belong in any of the other categories
*'''task''' is for anything that doesn't belong in any of the other categories
*Skilled users can also report their own patches using the '''patches''' type, but the average user shouldn't need this
*Skilled users can also report their own patches using the '''patches''' type, but the average user shouldn't need this
5. In Ticket Properties you should select which part of Pidgin your ticket is about. If you don't understand this, just leave it as '''unclassified'''
<ol><li>In Ticket Properties you should select which part of Pidgin your ticket is about. If you don't understand this, just leave it as '''unclassified'''
6. Now select the version of Pidgin you are using, and optionally write some keywords to make the ticket easier to find, and lastly click ''Submit ticket''.
</li><li>Now select the version of Pidgin you are using, and optionally write some keywords to make the ticket easier to find, and lastly click ''Submit ticket''.</li></ol>
 
=== Useful links ===
=== Useful links ===
* http://www.pidgin.im - Official webpage
* http://www.pidgin.im - Official webpage

2007年12月6日 (四) 15:38的版本

{{#ifexist: :Pidgin/zh | | {{#ifexist: Pidgin/zh | | {{#ifeq: {{#titleparts:Pidgin|1|-1|}} | zh | | }} }} }} {{#ifeq: {{#titleparts:Pidgin|1|-1|}} | zh | | }}

  1. title Pidgin Internet Messenger

Introduction

Pidgin?action=AttachFile&do=get&target=pidgin.2.png Pidgin is a well-known instant messaging (IM) client for a wide range of protocols, including MSN Messenger, AIM, Yahoo Messenger, Jabber, IRC, IRQ and Gadu-Gadu. It is available in the official Ubuntu repositories, but if you want you can install it from the official website instead.

Since Ubuntu is focused on stability, you will find that, apart from security updates and bugfixes, the Pidgin in the repositories will generally only be updated to a newer version with every new release of Ubuntu - which occurs approximately every 6 months.

Install Pidgin from repository

The recommended way to install Pidgin is through the official Ubuntu repositories. That way you'll get the supported version. Installing through the repositories is pretty straightforward:

  1. Go to Applications -> Add/Remove...
  2. Search for Pidgin and tick the box with Pidgin Internet Messenger.
  3. Press Apply Changes and, if asked, enter your password.

For more info about how to install software from the repositories, see InstallingSoftware.

Install current release from official website

You may sometimes want a newer version of Pidgin, and to get this, you will have to install it directly from the official website, but be aware that like any other application installed directly via a website such a version of Pidgin will not receive updates of any kind through Ubuntu's Update Manager! This section will explain the steps necessary to install Pidgin from the official website - in this example it's Pidgin 2.1.1, which, by the way, is already present in Ubuntu Gutsy's repositories.

Prepare for Installation

Removing Gaim

Before you start, you have to make sure Gaim, the predecessor of Pidgin, is not already installed. This can be done following these instructions:

  1. Go to System -> Administration -> Synaptic Package Manager
  2. Enter the password for your user account and press OK
  3. Press 'Search', and enter gaim into the search field
  4. If the gaim package is selected, then deselect it
  5. Press Apply.

Getting the necessary dependencies

Now, with a 'clean table', we can proceed. First, you need to install some libraries, which Pidgin will need in order to work:

  1. Go to Applications -> Accessories -> Terminal
  2. Type
    sudo apt-get install libgtk2.0-dev libxml2-dev gettext libnss-dev libnspr-dev
    
    to get the proper dependencies.
Optional libraries for extra features
  • If you wish to include spell checking, add libgtkspell-dev to that list.
  • If you wish to include ALSA or OSS for playing sounds, add libgstreamer0.10-dev to that list.
  • If you wish to include idle times based on keyboard/mouse usage, add libxss-dev to that list.

Downloading and extracting Pidgin

Your system should now be prepared to handle Pidgin, so it's time to get the Pidgin source code. This is pretty straightforward:

  1. Download pidgin-2.1.1.tar.bz2 from [1]
  2. When downloaded, right-click on pidgin-2.1.1.tar.bz2, which should be in your default Downloads-directory, and select «Extract Here»

Installation

Okay, so now you have all that you need, now it's all about compiling and installing:

  1. Go to Applications -> Accessories -> Terminal
  2. Type
    sudo apt-get install build-essential
    
    to install a build environment (see CompilingSoftware for further information)
  3. Change directory to the newly created pidgin-2.1.1 directory using the cd command. (If you don't know how to use cd, check "Commands" in the official Ubuntu documentation.)
  4. When you've navigated the terminal to the pidgin-2.1.1 directory, you have to type in the following in the Terminal:
    ./configure --enable-gnutls=yes
    

(Note: The --enable-gnutls=yes flag means SSL support will be compiled in, which is required for the MSN and Google Talk protocols.)

  1. Now Pidgin should be configured, and you should see a bunch of output on the screen. After it's finished configuring, it's time to create a makefile. In the same terminal, type:
    make
    
  2. Creating the makefile is also going to take a little while, so grab a cup of coffee while you wait :)
  3. When the make command has finished, it's time to actually install Pidgin. This is done by typing:
    make install
    
  4. When it's finished, then you should have Pidgin installed. Congratulations!

Clean up

With Pidgin installed, you have the option of doing a little cleaning up of the files that were created and used doing installation, but aren't used anymore:

  1. While remaining in the same terminal, type in
    make clean
    
  2. When finished, type in:
    make distclean
    
    to also remove the files that `./configure` created.

Other info

This section deals with other aspects of Pidgin than installing.

Bugs

Like all software, Pidgin has its share of bugs. However, you can help to improve Pidgin by reporting any bugs you may find. You can find all the currently reported bugs in the Pidgin bugtracker, which is located here. To report a bug, you need to do the following:

  1. Go to http://developer.pidgin.im
  2. Click "register" and pick a username and password
  3. Back at http://developer.pidgin.im click "New Ticket"
  4. Describe the bug, and mark what type it is. There are several types:
  • defect are problems/bugs in Pidgin
  • enhancement is an idea for how to improve the functionality of Pidgin. This corresponds to the "Wishlist" priority on UbuntuHelp:Launchpad
  • translation is for anything that has to do with a translation of Pidgin. E.g. typos in translations of Pidgin
  • plugin request is pretty self-explationary: Requests for additional functionality in Pidgin that aren't of "general" interest are generally better off as plugins than parts of Pidgin itself
  • task is for anything that doesn't belong in any of the other categories
  • Skilled users can also report their own patches using the patches type, but the average user shouldn't need this
  1. In Ticket Properties you should select which part of Pidgin your ticket is about. If you don't understand this, just leave it as unclassified
  2. Now select the version of Pidgin you are using, and optionally write some keywords to make the ticket easier to find, and lastly click Submit ticket.

Useful links