All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] dev-packages
Date: Fri, 3 Aug 2001 11:35:39 +0100	[thread overview]
Message-ID: <20010803113539.B1011@linuxcare.com> (raw)
In-Reply-To: <20010803132528.G9637@neep.com.au>; from andrew@neep.com.au on Fri, Aug 03, 2001 at 01:25:33PM +0800

On Fri, Aug 03, 2001 at 01:25:33PM +0800, Andrew Shugg wrote:
> Quoth Bjoern A. Zeeb:
> > On Thu, 2 Aug 2001, Matthew Wilcox wrote:
> > > They're all available in the debian archive.  I don't think we have
> > > plans to produce any more CDs until the Debian Woody release (probably
> > > December).
> > 
> > Could you point me to some URL (incl. subdir) please ?
> 
> If you've got apt configured (/etc/apt/apt.conf, /etc/apt/sources.list)
> then you don't need to worry about finding things directly.  After doing
> an 'apt-get update' to fetch the current Packages files and rebuild the
> local package database, you can say 'apt-cache search foo' and it will
> show you all the packages called foo or with foo in their description.
> A simple 'apt-get install foo-dev' will download and install the foo-dev
> package and any other package it may require according to its
> dependencies.

If for some reason you do want to find things directly, you should
be aware that pkgs live in a pool now, and you wont find much under
a sid/main/binary-hppa dir on your local mirror.  For example, libc6-dev
would be found under /pub/mirrors/debian/pool/main/g/glibc.  That one
is under 'g' because the source pkg is glibc.  But as Andrew said, apt
is right way to install things normally.

Richard

  reply	other threads:[~2001-08-03 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 21:06 [parisc-linux] dev-packages Bjoern A. Zeeb
2001-08-02 21:19 ` Matthew Wilcox
2001-08-03  4:56   ` Bjoern A. Zeeb
2001-08-03  5:25     ` Andrew Shugg
2001-08-03 10:35       ` Richard Hirst [this message]
2001-08-03 10:38         ` Bjoern A. Zeeb
2001-08-03 10:52           ` Andrew Shugg
2001-08-03 10:46         ` Andrew Shugg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010803113539.B1011@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.