Re: How does apt-get construt package uri?

[Try KDE <trykde@rogers.com>]

Thanks Rob.
Now, if all the three current distributions are in the same pool, it 
must be possible that the same package has three versions co-existing in 
the same directory, and only Packages.gz from different distribution  
can tell apt-get which version to pick up?

-tk

Rob Weir wrote:

> On Mon, Oct 14, 2002 at 08:46:20PM -0400, Try KDE wrote:
>  
>
> > Thanks to Eduardo Pereira Habkost's answer to the previous question - it 
> > works beautifully.
> >
> > Here is a harder question (in my opinion, anyway): given a http/ftp line in 
> > sources.list, what's apt's algorithm for retrieve the list of packages. For 
> > example, deb http://http.us.debian.org/debian/ testing main non-free 
> >   contrib
> >
> > will produce such an output from apt-get:
> >  Get:1 http://http.us.debian.org testing/main Packages [2036kB]
> >
> > So exactly what uri was constructed out of it? My browser says 
> > http://http.us.debian.org/testing/main doesn't exist. By the way, apt-get's 
> > manpage is very unclear in this aspects.
> >    
>
> The line 
> deb http://http.us.debian.org/debian/ testing main non-free contrib
> will tell apt to go and get the packages file (which lists info about
> each package) from 
> http://http.us.debian.org/debian/dists/testing/main/binary-<arch>/
>
> The actual packages are now stored in the `pool'.  That means that all
> the packages for all three current distributions (woody, sarge and sid)
> are in one big blob, in <first bit>/pool/.
>
> So, in conclusion:
> Packages.gz lives in
> <first bit>/dists/<distribution>/<section>/binary-<arch>/
> and packages live in
> <first bit>/pool/<section>/<you can figure the rest out>
>
> -rob
>