From: | Zac Medico <zmedico@g.o> | ||
---|---|---|---|
To: | gentoo-dev@l.g.o | ||
Subject: | Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-libs/glibc: glibc-2.14.1-r2.ebuild glibc-2.12.2.ebuild glibc-9999.ebuild glibc-2.15.ebuild glibc-2.10.1-r1.ebuild glibc-2.14.1-r1.ebuild glibc-2.14.ebuild glibc-2.13-r2.ebuild ChangeLog g | ||
Date: | Fri, 20 Jan 2012 00:40:22 | ||
Message-Id: | 4F18B7B0.9080003@gentoo.org | ||
In Reply to: | [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-libs/glibc: glibc-2.14.1-r2.ebuild glibc-2.12.2.ebuild glibc-9999.ebuild glibc-2.15.ebuild glibc-2.10.1-r1.ebuild glibc-2.14.1-r1.ebuild glibc-2.14.ebuild glibc-2.13-r2.ebuild ChangeLog g by Duncan <1i5t5.duncan@cox.net> |
1 | On 01/19/2012 03:38 PM, Duncan wrote: |
2 | > @ Zac: Could the output of an emerge --pretend (or --ask) account for |
3 | > -newuse, and include a boilerplate sentence or so about --exclude, if the |
4 | > proposed package merge list includes any same-version remerges due to |
5 | > --newuse? Or if tracking --newuse packages is too much, just trigger the |
6 | > boilerplate if --newuse is among the passed (or default) options. |
7 | |
8 | Maybe it would be enough to add a suggestion about --exclude in the |
9 | --newuse section of the emerge man page? I don't think this is confusing |
10 | enough to qualify for an interactive suggestion. |
11 | -- |
12 | Thanks, |
13 | Zac |