On Thu, 10 Jan 2002 11:32:10 -0600 Colin Watson <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 09, 2002 at 11:41:45PM -0600, Adam Majer wrote: > > On Thu, Jan 10, 2002 at 12:49:53AM +0000, Nicholas Avenell wrote: > > > Okay, A simple question, for which a simple answer would be appreciated: > > > > > > I am looking for a simple, step by set guide to turning a directory > > > full of .deb files into something I can access with a sources.list entry. > > > > > > In this case, /var/cache/apt/archives/. > > > > > > it's currently set up as an nfs share accross the network, which is > > > sub-optimal. I can work out how to get at it via ftp or http, but I've > > > no idea how to make it able to be seen via an sources.list file. > > > > To access these .deb files via apt, you need Packages file. To build > > Packages, just look at dpkg-scanpackages. To create an "override" > > file, just > > > > touch override > > > > ie. empty file since you don't ususally need override. > > Or indeed just use /dev/null. > > Remember to gzip the Packages file after creating it with > dpkg-scanpackages, otherwise apt won't see it (and you'll get a > misleading error message). Hmm, maybe that reduces the file space. But I have NEVER gzip'ped the Packages file for my internal apt-get source (which tracks unstable). apt-get has no problems seeing it. Is this one of those potato-does-it-differently things?
