On Tue, Jul 03, 2012 at 12:17:39PM -0600, Paul E Condon wrote:
.......snip......
>
> Let me join in the discussion of what I intended by my badly
> worded request:
>
> 1. I need a way of learning the name of the package that might help
> with some problem, a place on the web where I can pick up search terms
> on a topic with which I am not familiar. At the beginning of my
> search, I simply don't know what to type in the search box. In the
> particular case of backports of packages that I am already using
> and are serving me well enough as is, but might have a backport that
> is actually much better, how do I discover that backport? But more
> likely situation is that I have tried and found wanting the package
> in the original release, but would revisit the issue if I knew their
> was a backport. Tracking backports of software that I am somehow
> able to live without is not something to which I can allot much time.
> But I might be missing out on some really neat stuff.
>
> 2. If I do decide to put squeeze-backports in my sources.list, will
> the backported packages be displayed in the interactive browser?
>
> 3. If they are displayed in interactive mode, will I be able to tell
> that they are backports? (so that I can exercise that extra caution
> that has been recommended in this thread)
>
> These are questions that are quite low priority because I am generally
> quite satisfied with the pace of development in Debian. If the
> answers indicate that using backports is not for me, I'll not
> complain.
As you may or may not have been previously advised,
http://packages.debian.org/squeeze-backports/
--
Bob Holtzman
If you think you're getting free lunch,
check the price of the beer.
Key ID: 8D549279
Attachment:
signature.asc
Description: Digital signature