Re: Packages in pool and woody

[Lauri Tischler <lauri.tischler@iki.fi>]

Peter Makholm wrote:
> 
> } So, how will this actually work, since we have package pools? Basically,
> } we'll end up with something like the following:
> }
> }       stable:   potato
> }       testing:  woody
> }       unstable: sid

Wasn't the original definition something like:
      stable:  potato
    unstable:  woody
experimental:  sid

My question really was about actual *.deb files themselves, if we are using
pool why are there any files in potato|woody|sid at all
Shouldn't they consist only of Packages.gz file(s) which then picks files from
pool.

Example:

pool contains in  /pool/non-US/main/a/apache-ssl  files
apache-ssl_1.3.14.2+1.42-1_i386.deb  and
apache-ssl_1.3.14.2+1.42-2_i386.deb

woody contains in /dists/woody/non-US/main/binary-i386  file
apache-ssl_1.3.12.2+1.41-2.deb

First entry in file /dists/woody/non-US/main/binary-i386/Packages.gz happens
to be
 ....
Filename: pool/non-US/main/a/apache-ssl/apache-ssl_1.3.14.2+1.42-2_i386.deb
Size: 447332
 ....

So the question remains, why the file 
/dists/woody/non-US/main/binary-i386/apache-ssl_1.3.12.2+1.41-2.deb
still exists ???

If a file is not referenced in any Packages.gz then it should dissappear,
shouldn't it ....

...  puuff, I'm gone  .....
-- 
lauri.tischler@iki.fi * Man created god as His image *
                      *  Man has horrid imagination  *