All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Shugg <andrew@neep.com.au>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] dev-packages
Date: Fri, 3 Aug 2001 13:25:33 +0800	[thread overview]
Message-ID: <20010803132528.G9637@neep.com.au> (raw)
In-Reply-To: <Pine.BSF.4.30.0108030645560.38503-100000@noc.zabbadoz.net>; from bzeeb+hplinux@zabbadoz.net on Fri, Aug 03, 2001 at 06:56:08AM +0200

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.

For more info & discussion on actual Debian issues rather than the
actual development of the hppa-linux kernel and toolchain have a look at
the debian-hppa mailing list (on the Debian website).

Andrew.

-- 
Andrew Shugg <andrew@neep.com.au>                   http://www.neep.com.au/

"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there?  Well I'd like to meet him.  I could do with a good laugh."

  reply	other threads:[~2001-08-03  5:25 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 [this message]
2001-08-03 10:35       ` Richard Hirst
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=20010803132528.G9637@neep.com.au \
    --to=andrew@neep.com.au \
    --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.