public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] `paludis --info' is not like `emerge --info'
Date: Wed, 18 Feb 2009 22:55:06 +0000	[thread overview]
Message-ID: <20090218225506.14b91815@snowcone> (raw)
In-Reply-To: <20090218232212.5452b86d@epia.jer-c2.orkz.net>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

On Wed, 18 Feb 2009 23:22:12 +0100
Jeroen Roovers <jer@gentoo.org> wrote:
> Paludis users often seem to think that `paludis --info' and `emerge
> --info' are interchangeable, whereas a quick inspection reveals to
> even the most casual user that the former only intends to inform about
> paludis' own compile time and run time configuration, whereas the
> latter includes information about a number of critical system
> packages, the global USE and USE_EXPAND variables and GENTOO_MIRRORS
> variable, to name a few.

...which is why you ask for 'paludis --info pkg', not 'paludis --info'.
That way you get accurate information about pkg, even when users have
per-package use flags configured. Much more useful than Portage's
misleading output, which just gives global configuration and
completely ignores everything else.

Heck, Paludis even tells you this if you run --info without a spec:

> No packages were specified on the command line, so detailed
> information is not available (Paludis can display detailed information
> for both installed and installable packages).

Please try harder next time.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-02-18 22:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 22:22 [gentoo-dev] `paludis --info' is not like `emerge --info' Jeroen Roovers
2009-02-18 22:35 ` Dawid Węgliński
2009-02-18 22:38   ` Jeroen Roovers
2009-02-18 22:55 ` Ciaran McCreesh [this message]
2009-02-18 23:03   ` Jeroen Roovers
2009-02-18 23:24     ` Ciaran McCreesh
2009-02-18 23:39       ` Stelian Ionescu
2009-02-18 23:42         ` Ciaran McCreesh
2009-02-18 23:48       ` Jeroen Roovers
2009-02-18 23:08   ` Jeroen Roovers
2009-04-04 13:17   ` Peter Alfredsen
2009-04-04 13:47     ` Ciaran McCreesh
2009-04-04 16:12       ` Thilo Bangert
2009-04-04 16:36         ` Matti Bickel
2009-04-05 20:41         ` Timothy Redaelli
2009-04-06  3:29           ` Andrew D Kirch
2009-04-06  3:35             ` Andrew Gaffney
2009-04-06  3:49               ` Andrew D Kirch
2009-04-06  3:55                 ` Nirbheek Chauhan
2009-04-06  4:42                   ` Andrew D Kirch
2009-04-06 16:25                     ` Richard Freeman
2009-04-06  9:32             ` Timothy Redaelli
2009-04-06 10:16               ` [gentoo-dev] " Duncan
2009-04-06  8:11           ` [gentoo-dev] " Peter Volkov
2009-04-08 14:36             ` Jeroen Roovers
2009-04-28 20:15               ` Peter Volkov
2009-04-08 19:13             ` Zac Medico
2009-04-13 12:21     ` Sebastian Pipping
2009-04-13 12:29       ` Ciaran McCreesh
2009-04-13 21:50         ` Sebastian Pipping
2009-04-13 21:55           ` Ciaran McCreesh
2009-04-14  0:29             ` Richard Freeman
2009-04-14  1:32               ` [gentoo-dev] " Duncan
2009-05-09 21:14 ` [gentoo-dev] " Thomas Anderson
2009-05-10  3:23   ` Nirbheek Chauhan
2009-05-10  9:21     ` David Leverton

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=20090218225506.14b91815@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox