americas-army-221-r1 revsion bump really needed?

[firephoto]

So as my system sits for 10 minutes unpacking the aa tarball for the r1 bump that's for a dedicated server patch, I sit here wondering what the point is since I don't have "dedicated" in my use flag.
Wouldn't it have been easier to push the patch through the sync process (my package.unmask gets changed a lot magicly lately) or just leave it without a revision and make a note in the change log?

Seems kind of silly for 10 minutes of time spent for nothing.

[Lews_Therin]

If there was no point to upgrading, why did you do so?

[firephoto]

I shouldn't have to mask off updates that shouldn't apply to begin with per the USE flags.

I see lots of minor patches come through on ebuilds daily but there's no revision bumps, just a note in the changelog so if you do re-emerge you get a little download sometimes and the patch applied.

It just seems like it could have been handled different for such a minor thing and since it's binary install anyway nothing from the archive that gets unpacked again is going to change.

[Lews_Therin]

Again, why mask it off? Do you reguarly run an emerge -uD world or something?

[firephoto]

ummmm yes I do as a matter of fact.

[ghost_adsf]

Sounds like someone should run, emerge -uDp world - first from now on.

[firephoto]

Ummmm I did, and why should I have to cancel it (I use -a), mask the package, then start it again just because there's a patch that got a revision bump that is only specific to a use flag you might use. I just feel it should have been patched and left as is and anyone needing that can re-emerge it. It's not like it "fixed" anything that was broke.

I'll just take my incompetent self back in the hole some think I seem to have crawled out of.