On Fri, 25 Jan 2008 19:30:55 -0500 David Relson <[EMAIL PROTECTED]> wrote:
> I've been experimenting with paludis for the last month or two to
> compare it with emerge. For my periodic "update world" runs the two
> programs seem functionally comparable. Paludis is, however, more
> verbose and I'm not liking that aspect.
>
> My typical emerge command is "emerge -auDtqv world" and produces:
>
> [ebuild UD] kde-base/kde-3.5.7 [3.5.8] USE="..."
> [ebuild U ] sys-apps/paludis-0.26.0_alpha9 [0.26.0_alpha7]
> USE="..." [noomerge ] kde-base/kde-3.5.7 [3.5.8] USE="..."
> [nomerge ] sys-apps/paludis-0.26.0_alpha9 [0.26.0_alpha7] ...
> [ebuild U ] dev-libs/boost-1.34.1-r2 [1.34.1-r1] ...
> [ebuild UD] app-misc/mime-types-5 [7] ..
>
> Would you like to merge these packages? [Yes/No] no
>
> Quitting.
>
> I like the one brevity as I can see a lot of information and then
> decide whether to go ahead or not.
>
> "paludis --show-use-descriptions none -p -i world" lets me see
> what's going to happen. On the down side, I need to run it a
> second time (without the "-p") to install the packages. Also,
> paludis first prints a bunch of informational messages and then
> prints 4 info lines per package.
>
> Have I overlooked an option comparable to "--ask" ?
>
No, Paludis is non-interactive.
> Have I overlooked an option to suppress the initial messages.
>
Use --compact to compress the package output and --log-level to control
the amount of informational messages.
> Thanks.
>
> David
Brian
signature.asc
Description: PGP signature
