| 1 |
On Wed, 18 Feb 2009 23:22:12 +0100 |
| 2 |
Jeroen Roovers <jer@g.o> wrote: |
| 3 |
> Paludis users often seem to think that `paludis --info' and `emerge |
| 4 |
> --info' are interchangeable, whereas a quick inspection reveals to |
| 5 |
> even the most casual user that the former only intends to inform about |
| 6 |
> paludis' own compile time and run time configuration, whereas the |
| 7 |
> latter includes information about a number of critical system |
| 8 |
> packages, the global USE and USE_EXPAND variables and GENTOO_MIRRORS |
| 9 |
> variable, to name a few. |
| 10 |
|
| 11 |
...which is why you ask for 'paludis --info pkg', not 'paludis --info'. |
| 12 |
That way you get accurate information about pkg, even when users have |
| 13 |
per-package use flags configured. Much more useful than Portage's |
| 14 |
misleading output, which just gives global configuration and |
| 15 |
completely ignores everything else. |
| 16 |
|
| 17 |
Heck, Paludis even tells you this if you run --info without a spec: |
| 18 |
|
| 19 |
> No packages were specified on the command line, so detailed |
| 20 |
> information is not available (Paludis can display detailed information |
| 21 |
> for both installed and installable packages). |
| 22 |
|
| 23 |
Please try harder next time. |
| 24 |
|
| 25 |
-- |
| 26 |
Ciaran McCreesh |
Archives