个人工具

“UbuntuHelp:Repositories/Personal”的版本间的差异

来自Ubuntu中文

跳转至: 导航, 搜索
第4行: 第4行:
 
== Introduction ==
 
== Introduction ==
 
There are often a few packages that you want to install that don't exist in the Ubuntu repositories. If they have any dependencies on other packages, trying to using '''dpkg''' can drop you into "dpkg hell", and having '''apt''' resolve those dependencies for you would really help.
 
There are often a few packages that you want to install that don't exist in the Ubuntu repositories. If they have any dependencies on other packages, trying to using '''dpkg''' can drop you into "dpkg hell", and having '''apt''' resolve those dependencies for you would really help.
There are full blown methods of creating your own local repository, such as [[UbuntuHelp:Debarchiver|Debarchiver]] or [[UbuntuHelp:Dak|Dak]]. These are overkill, when all you want is a means of resolving dependencies of the handful of packages you've downloaded from the web (not for an entire repository that you want to use without Internet connection; for this use [[UbuntuHelp:AptGet/Offline/Repository|AptGet/Offline/Repository]]. A simple solution is to use '''dpkg-scanpackages''', which will build a repository you can add to your sources.list.
+
There are full blown methods of creating your own local repository, such as [[UbuntuHelp:Debarchiver|Debarchiver]] or [[UbuntuHelp:Dak|Dak]]. These are overkill, when all you want is a means of resolving dependencies of the handful of packages you've downloaded from the web (not for an entire repository that you want to use without Internet connection; for this use [[UbuntuHelp:AptGet/Offline/Repository|AptGet/Offline/Repository]]). A simple solution is to use '''dpkg-scanpackages''', which will build a repository you can add to your sources.list.
 
== Creating a Personal Repository ==
 
== Creating a Personal Repository ==
 
There are 4 steps to setting up a simple repository for yourself
 
There are 4 steps to setting up a simple repository for yourself
第26行: 第26行:
 
If you have installed apt-cacher you will have additional packages stored in its /packages directory.
 
If you have installed apt-cacher you will have additional packages stored in its /packages directory.
 
=== The Script update-mydebs ===
 
=== The Script update-mydebs ===
It's a simple two liner:
+
It's a simple three liner:
 
<pre><nowiki>
 
<pre><nowiki>
#! /bin/bash
+
#! /bin/bash
cd /usr/local/mydebs
+
cd /usr/local/mydebs
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz
+
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz
 
</nowiki></pre>
 
</nowiki></pre>
 
Cut and paste the above into gedit, and save it as '''update-mydebs''' in ~/bin. (the tilde '~' means your home directory. If ~/bin does not exist, create it: Ubuntu will put that directory in your PATH. It's a good place to put personal scripts). Next, make the script executable:
 
Cut and paste the above into gedit, and save it as '''update-mydebs''' in ~/bin. (the tilde '~' means your home directory. If ~/bin does not exist, create it: Ubuntu will put that directory in your PATH. It's a good place to put personal scripts). Next, make the script executable:
第37行: 第37行:
 
</nowiki></pre>
 
</nowiki></pre>
 
'''How the script works:'''
 
'''How the script works:'''
'''dpkg-scanpackages''' looks at all the packages in mydebs, and the output is compressed and written to a file (Packages.gz) that '''apt-get update''' can read (see below for a reference that explains this in excruciating detail). /dev/null is an empty file; it is a substitute for an override file which holds some additional information about the packages, which in this case is not really needed. Again, see the reference at the bottom if you really want to know about it.
+
'''dpkg-scanpackages''' looks at all the packages in mydebs, and the output is compressed and written to a file (Packages.gz) that '''apt-get update''' can read (see below for a reference that explains this in excruciating detail). /dev/null is an empty file; it is a substitute for an override file which holds some additional information about the packages, which in this case is not really needed. See deb-override(5) if you want to know about it.
 
=== Sources.list ===
 
=== Sources.list ===
 
add the line
 
add the line
第54行: 第54行:
 
Badly made packages will probably fail, but you won't have endured dpkg hell.
 
Badly made packages will probably fail, but you won't have endured dpkg hell.
 
== References ==
 
== References ==
[[UbuntuHelp:AptGetHowto|AptGetHowto]]
+
* [[UbuntuHelp:AptGetHowto|AptGetHowto]]
[http://www.debian.org/doc/manuals/maint-guide/index.en.html Debian New Maintainers Guide] (this is the exruciating one)
+
* [http://www.debian.org/doc/manuals/maint-guide/index.en.html Debian New Maintainers Guide] (this is the exruciating one)
 
----
 
----
[[category:CategoryDocumentation]]
 
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2009年5月12日 (二) 18:37的版本


General information: Repositories in Ubuntu

Introduction

There are often a few packages that you want to install that don't exist in the Ubuntu repositories. If they have any dependencies on other packages, trying to using dpkg can drop you into "dpkg hell", and having apt resolve those dependencies for you would really help. There are full blown methods of creating your own local repository, such as Debarchiver or Dak. These are overkill, when all you want is a means of resolving dependencies of the handful of packages you've downloaded from the web (not for an entire repository that you want to use without Internet connection; for this use AptGet/Offline/Repository). A simple solution is to use dpkg-scanpackages, which will build a repository you can add to your sources.list.

Creating a Personal Repository

There are 4 steps to setting up a simple repository for yourself

  1. Install dpkg-dev
  2. Put the packages in a directory
  3. Create a script that will scan the packages and create a file apt-get update can read
  4. Add a line to your sources.list pointing at your repository

Install dpkg-dev

Type in a terminal

apt-get install dpkg-dev

The Directory

Create a directory where you will keep your packages. For this example, we'll use /usr/local/mydebs.

mkdir /usr/local/mydebs

Now move your packages into the directory you've just created. Previously downloaded Packages are generally stored on your system in the /var/cache/apt/archives directory. If you have installed apt-cacher you will have additional packages stored in its /packages directory.

The Script update-mydebs

It's a simple three liner:

 #! /bin/bash
 cd /usr/local/mydebs
 dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

Cut and paste the above into gedit, and save it as update-mydebs in ~/bin. (the tilde '~' means your home directory. If ~/bin does not exist, create it: Ubuntu will put that directory in your PATH. It's a good place to put personal scripts). Next, make the script executable:

chmod u+x ~/bin/update-mydebs

How the script works: dpkg-scanpackages looks at all the packages in mydebs, and the output is compressed and written to a file (Packages.gz) that apt-get update can read (see below for a reference that explains this in excruciating detail). /dev/null is an empty file; it is a substitute for an override file which holds some additional information about the packages, which in this case is not really needed. See deb-override(5) if you want to know about it.

Sources.list

add the line

deb file:/usr/local/mydebs ./

to your /etc/apt/sources.list, and you're done. See Repositories/Ubuntu.

Using the Repository

Whenever you put a new deb in the mydebs directory, run

sudo update-mydebs
sudo apt-get update

Now your local packages can be manipulated with Synaptic, aptitude and the apt commands: apt-get, apt-cache, etc. When you attempt to apt-get install, any dependencies will be resolved for you, as long as they can be met. Badly made packages will probably fail, but you won't have endured dpkg hell.

References