On Aug 20, Eric Winger ([EMAIL PROTECTED]) wrote: > Hi! > > Continuing our investigation into debian packages, we'd like to be able > to create our own internal archive/repository for just our packages. > Then change our sources.list file to point at that and be able to use > the apt-get engines to update our code on any machine at any of our > facilities. > > I don't see much information on what an archive is, how one > creates/administers one, how one puts packages in one and identifies it > to sources.list. I suspect that info is there, I'm just missing it. > http://www.debian.org/doc/developers-reference talks about the debian > archive, but not maintaining your own. > > So, two questions: > > * Is this a reasonable way to maintain our internal packages - ie a > seperate archive? Or is there a better way. > * If this is the most reasonable way, where is the information on > building/maintaining your own archive. > > btw - we're only talking about a few packages. < 10. > > thx much, > > Eric
Sounds reasonable. Did you read the APT HOWTO? -- Neil Roeth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
