public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sandy McArthur <sandymac@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Additional information to output: emerge -pv
Date: Thu, 25 Aug 2005 10:15:26 -0400	[thread overview]
Message-ID: <6bde122b05082507152a9f4d01@mail.gmail.com> (raw)
In-Reply-To: <430D29C3.5010004@wmich.edu>

How about making it so you need two -v switchs (eg: -vv) to get the
long listing? I use `emerge world -puv` all the time and don 't want
to have to scroll through so much stuff.

On 8/24/05, Dustin Spicuzza <dustin.spicuzza@wmich.edu> wrote:
> Hey,
> 
> I've been using Gentoo for a couple of years now... and portage was the
> #1 reason I kept using Gentoo over other Linux distros... and why I'm
> still using it.
> 
> Something that's always bugged me a lot is USE flags. Which, while I
> think that they are one of the best things about portage, I think that
> they are also one of the more annoying features as well... it can be
> relatively annoying to configure it all up. Especially researching what
> they are... yes, it just takes a little bit of effort to find them, but
> why not make it slightly easier?
> 
> Anyways, I made a patch (against Portage 2.0.51.22-r2, attached as
> verbose_use_patch.tar) that adds the description of each USE flag to the
> 'emerge -pv <package>' command. The output for openoffice, for example,
> looks something like this...
> 
> [ebuild  N    ] app-office/openoffice-1.1.4-r1  -curl -hardened -java
> +kde -nptl +zlib 215,331 kB
>   *  curl - Adds support for client-side URL transfer library
>   *  hardened - activate default security enhancements for toolchain
> (gcc, glibc, binutils)
>   *  java - Adds support for Java
>   *  kde - Adds support for kde-base/kde (K Desktop Enviroment)
>   *  nptl - Enable support for Native POSIX Threads Library, the new
> threading module (requires linux-2.6 or better usually)
>   *  zlib - Adds support for zlib (de)compression
> 
> And, it does this for each package (only for verbose obviously) Its a
> very small, non-invasive patch, and quite small (a routine in
> portage_util.py, and 5 lines of code in emerge).
> 
> I attached the patch here because I wasn't quite sure of the proper
> procedure for patch submission... anyways, thanks for all your work!
> Hopefully in the future I can contribute to this project.
> 
> Dustin Spicuzza
> 
> 
> 


-- 
Sandy McArthur

"Government big enough to supply everything you
need is big enough to take everything you have ...
The course of history shows that as a government
grows, liberty decreases." -- Thomas Jefferson

-- 
gentoo-portage-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-08-25 14:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25  2:15 [gentoo-portage-dev] Additional information to output: emerge -pv Dustin Spicuzza
2005-08-25  9:58 ` Simon Stelling
2005-08-25  9:59 ` Paul de Vrieze
2005-08-25 14:15 ` Sandy McArthur [this message]
2005-08-25 16:14   ` Brian Harring
2005-08-25 16:28     ` Brian Harring
2005-08-25 20:42 ` Alec Warner
  -- strict thread matches above, loose matches on Subject: below --
2005-08-25 17:44 Dustin Spicuzza
2005-08-25 21:57 ` Brian Harring
2005-08-25 18:15   ` Dustin Spicuzza
2005-08-25 22:24     ` Brian Harring
2005-08-25 17:54 Dustin Spicuzza
2005-08-25 18:22 ` Thomas de Grenier de Latour

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=6bde122b05082507152a9f4d01@mail.gmail.com \
    --to=sandymac@gentoo.org \
    --cc=gentoo-portage-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