Changes between Version 2 and Version 3 of SourcePackages


Ignore:
Timestamp:
01/23/13 17:12:51 (9 years ago)
Author:
jdreed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SourcePackages

    v2 v3  
    4646As with the `dpkg` command, the APT front end is more commonly used.  The same repositories which contain binary packages also contain binary source packages.  It's possible to get the source package for any binary package with the `apt-get source` command.  This command downloads the source package to the current directory and unpacks it for you.  Note that a single source package may generate multiple binary packages.  For example, if you have the binary package `foo-utils`, which might also come with the package `foo-doc`, the source for both of those would likely be in the `foo` package, so `apt-get source foo-doc` would get you the same source as `apt-get source foo-utils`.  However, with APT, you don't have to worry about this -- it will determine what the appropriate source package is, and it will get it for you. 
    4747 
     48=== dget === 
     49 
     50If you just download the `.dsc` file, and try to install it, you'll get an error.  For a `.dsc` hosted on the web, you can use the `dget` command, which will fetch the `.dsc` file and then fetch the relevant `.tar.gz` and/or `.diff.gz` files. 
     51 
     52 
    4853We now have a source package, which is typically unpacked into a directory with the name of the package and its version (e.g. rpncalc-0.1).  If we look in that directory, we'll see the software, as well as a `debian` directory.  The `debian` directory contains a number of special files necessary to build the package. 
    4954