

Code: Select all
# diff digest-kdelibs-3.5.1 digest-kdelibs-3.5.0-r2
1c1
< MD5 2a22193ae7c23f3759b02723dab02d30 kdelibs-3.5.1.tar.bz2 15459894
---
> MD5 2b11d654e2ea1a3cd16dcfdcbb7d1915 kdelibs-3.5.0.tar.bz2 15379557
i like gentoo just as much as the next guy, but suse and ubuntu packages usually come with the release announcement, whereas with gentoo you have to spend a while compiling them.friedmud wrote:It's not really an annoyance... I'm mostly just excited to see a new release coming down the pipe....
The up to the minuteness is why I use Gentoo in the first place
Friedmud

Yes. This topic returns every time a new KDE release is expected. I don't understand why those ebuilds are in portage already. What happens with the MDsums? These are unknown until the tarballs are released. There is no point in releasing the ebuilds so early.6thpink wrote:Each new release the same, here is the thread for 3.5.0: http://forums.gentoo.org/viewtopic-t-40 ... nload.html
germanbox,germanobax wrote:The best thing is that I unmerged my KDE-3.5.0, to realize later that the new packages aren't available yet.
I think that updating to 3.5.1 it will update all the split ebuilds from 3.5.0 to 3.5.1 regardless of the changes in the ebuild. The split ebuilds would allow to pach specific components of kdenetwork for instance. So split ebuilds would be helpful for a bug in kopete and not to recompile the whole kdenetwork. But if there is a new release, all splits ebuild will be recompiled. That is how I understand this.jdgill0 wrote:
germanbox,
Why do you unmerge all of KDE-3.5.0 to emerge KDE-3.5.1? If you are using the split ebuilds, this causes you to waste time. Not all packages in KDE-3.5.1 will be updated/different than those in 3.5.0. The split ebuilds method will in reality only update those that need updating. Maybe I am wrong about this, but that was my understanding as part of the reason Gentoo moved to the split ebuilds.
Not meaning to get off topic here.

In case the tarballs are released at the time the gentoo kde developers are asleep and ebuilds are not immediately available, people start bitching here in the forums. If they're there in advance, people can start compiling and bitch about other things.irondog wrote:I don't understand why those ebuilds are in portage already.
No, they are the same. The tarballs that are released are the same that are send to distribution developers some time before to let them build binary packages (or ebuilds).irondog wrote:What happens with the MDsums? These are unknown until the tarballs are released.
I'd say there's no point in holding them back, except that people don't read the package.mask comment and ask the same questions again and again for each releaseirondog wrote:There is no point in releasing the ebuilds so early.
