| 1 |
On Wed, 23 Jan 2013 17:37:19 -0600 |
| 2 |
Bruce Hill <daddy@×××××××××××××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Wed, Jan 23, 2013 at 11:15:10PM +0000, Neil Bothwick wrote: |
| 5 |
> > |
| 6 |
> > That's right. So --changed-use only reemerges the package if the |
| 7 |
> > change only affects your system, whereas -N will rebuild it even if |
| 8 |
> > the changed flag is of no interest to you, such as when a flag you |
| 9 |
> > were not using is removed. It saves recompiling packages for no |
| 10 |
> > reason, which is presumably the reason it was added, it is a newer |
| 11 |
> > option than -N. |
| 12 |
> |
| 13 |
> The purpose of -a (ask) is so you can see the stuff before taking |
| 14 |
> action, and if it needs rebuilding then do it. Nothing is rebuilt |
| 15 |
> just because it shows up in the output; but not seeing changes to a |
| 16 |
> package you use that were made is not too bright. |
| 17 |
|
| 18 |
A new capability merits a revision bump if it's significant enough that |
| 19 |
people need to see the change. I'm content to let the devs make that |
| 20 |
call, but that may be because I am not too bright. |
Archives