On Wed, 20 Aug 2003 23:51:27 -0400, "Christopher W. Curtis"
<[EMAIL PROTECTED]> wrote:
>A poor man's version would be: "man dpkg-scanpackages"
apt-ftparchive does a better job than dpkg-scanpackages.
Greetings
Marc
--
-- !! No courtesy copies, please !!
On Wed, 20 Aug 2003 23:51:27 -0400, "Christopher W. Curtis"
<[EMAIL PROTECTED]> wrote:
>A poor man's version would be: "man dpkg-scanpackages"
apt-ftparchive does a better job than dpkg-scanpackages.
Greetings
Marc
--
-- !! No courtesy copies, please !!
On Thu, Aug 21, 2003 at 02:40:27PM +0200, Roland Mas wrote:
> Eric Winger (2003-08-20 16:05:33 -0700) :
>
> > So, two questions:
> >
> > * Is this a reasonable way to maintain our internal packages - ie a
> > seperate archive? Or is there a better way.
>
> It's the best way I've found.
>
> > * I
Christopher W. Curtis wrote:
A quick google for "apt repository howto", besides pulling up a
surprising number of links about RPMs, also brings up these two:
http://www.debian.org/doc/manuals/repository-howto/repository-howto.html
Thanks to everyone for their responses. This link has prove
On Thu, Aug 21, 2003 at 02:40:27PM +0200, Roland Mas wrote:
> Eric Winger (2003-08-20 16:05:33 -0700) :
>
> > So, two questions:
> >
> > * Is this a reasonable way to maintain our internal packages - ie a
> > seperate archive? Or is there a better way.
>
> It's the best way I've found.
>
> > * I
Christopher W. Curtis wrote:
A quick google for "apt repository howto", besides pulling up a
surprising number of links about RPMs, also brings up these two:
http://www.debian.org/doc/manuals/repository-howto/repository-howto.html
Thanks to everyone for their responses. This link has proved ver
Eric Winger (2003-08-20 16:05:33 -0700) :
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
It's the best way I've found.
> * If this is the most reasonable way, where is the information on
> building/mainta
Eric Winger (2003-08-20 16:05:33 -0700) :
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
It's the best way I've found.
> * If this is the most reasonable way, where is the information on
> building/mainta
Eric Winger <[EMAIL PROTECTED]> writes:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Its realy easy for small repositories (say <100 packages so this
applies to you) but you need proper management script
Eric Winger <[EMAIL PROTECTED]> writes:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Its realy easy for small repositories (say <100 packages so this
applies to you) but you need proper management script
On Wed, Aug 20, 2003 at 04:05:33PM -0700, Eric Winger wrote:
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
It seems a reasonable way to have some packages that are specific for
your situation.
> * If this is the most reasonable
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
On 08/20/03 19:05, Eric Winger wrote:
> Continuing our investigation into debian packages, we'd like to be able
> to create our own internal archive/repository for just our packages.
...
> I don't see much information on what an archive is, how one
> creates/administers one, how one puts packages
Eric Winger wrote:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Yes.
> * If this is the most reasonable way, where is the information on
> building/maintaining your own archive.
You need to create a rep
On Wed, Aug 20, 2003 at 04:05:33PM -0700, Eric Winger wrote:
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
It seems a reasonable way to have some packages that are specific for
your situation.
> * If this is the most reasonable
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
On 08/20/03 19:05, Eric Winger wrote:
> Continuing our investigation into debian packages, we'd like to be able
> to create our own internal archive/repository for just our packages.
...
> I don't see much information on what an archive is, how one
> creates/administers one, how one puts packages
Eric Winger wrote:
> So, two questions:
>
> * Is this a reasonable way to maintain our internal packages - ie a
> seperate archive? Or is there a better way.
Yes.
> * If this is the most reasonable way, where is the information on
> building/maintaining your own archive.
You need to create a rep
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
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.
20 matches
Mail list logo
