On Tue, Jan 13, 2009 at 5:55 PM, b.n. <[email protected]> wrote: > Paul Hartman ha scritto: >> On Tue, Jan 13, 2009 at 9:44 AM, Paul Hartman >> <[email protected]> wrote: >>> Hi, >>> >>> I normally do "emerge -uDvN @world" (or in other words "emerge >>> --update --deep --verbose --newuse @world"). Right now, it tells me >>> this: >>> >>> Total: 0 packages, Size of downloads: 0 kB >>> >>> I also --depclean on a regular basis to remove any unneeded packages. >>> Right now, it tells me this: >>> >>> No packages selected for removal by depclean >>> >>> Based on those two commands, I'm led to believe I have a fully updated >>> system. So, then, I am curious why when I do "emerge -e @world" it >>> tells me this: >>> >>> Total: 1432 packages (9 upgrades, 2 downgrades, 14 new, 1407 >>> reinstalls, 1 interactive), Size of downloads: 76,235 kB >>> >>> How is that possible? Where do those upgrades, downgrades and new >>> packages come from? What is missing from my traditional "-uDvN" >>> command that is causing me to miss some of those updates? >>> >>> Thanks, >>> Paul >> >> Before anyone responds I will throw in my theory :) >> >> I'm using ~amd64 and I suppose perhaps the ebuilds have changed since >> I installed them, but have not had a version increase. > > It's 4 years I'm using Gentoo and I can still be surprised by it. :) > This doesn't look right. Why do devs upgrade ebuilds and do not increase > the -rX versioning? > > m. > >
Good question. If you look at the ChangeLog from openoffice-3.0.0 you can see it was marked stable on x86 & amd64 in 18 Oct 2008 but the ebuild has had some dramatic changes in the time since then, including bug fixes, patches, etc. My /guess/ is that since OpenOffice is such a huge package, if they bump the -r1 -r2 -r3 very often and people have 9 hours of compiling each time, it will annoy the gentoo population. So, instead, they use the idea that if nothing is gained by someone with a working openoffice, no reason to fix it (but if someone had a problem they can just "re-emerge openoffice and see if it works now").
