ANN: split kde ebuilds

danarmak · Posted: Sat Jan 15, 2005 8:07 pm Post subject: ANN: split kde ebuilds

Hi all -
I hereby officially announce the split KDE ebuilds for 3.4.0_beta1. More info is here.

Apologies to all of the people who tried to emerge the variously incomplete or broken versions that were in portage yesterday. Importing 350 ebuilds and 3 eclasses and a forest of deps isn't easy, so I did it piecemeal. If anything is still broken, bug us.

Enjoy! There's still a lot to be done, but the split ebuilds are already at least as good as the monolithic ones.

made sticky --Earthwings
_________________
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel

ralph · Advocate Joined: 02 Mar 2003 Posts: 2001 Location: Hamburg

I'm compiling right now.

Just wanted to say a big thanks to all those involved. This has probably been a lot of work, but it's really appreciated.
_________________
The computer can't tell you the emotional story. It can give you the exact mathematical design, but what's missing is the eyebrows.
- Frank Zappa

Kagerato · Tux's lil' helper Joined: 01 Dec 2004 Posts: 81

Excellent work. I particularly despised the monolithic ebuilds, so it's wonderful to see such an enormous undertaking as this functioning so quickly.

Thanks to all who contributed.

WladyX · Guru Joined: 25 Nov 2004 Posts: 503 Location: Romania

You will install 200 individual packages and then want to remove them,you will have to emerge unmerge pack1 pack2....pack200, right? I mean will there be something like emerge unmerge kde?
_________________
We are not alone.

Gaspode · n00b Joined: 02 Oct 2004 Posts: 36

I guess if you did emerge the 200 packages with 'emerge kde-meta' then you could probably do 'emerge -C kde-meta && emerge --depclean' to get rid of them. If you emerge the packages manually, then you would need to remove them from the world file first...

<OT>
But I also would like to see some option in portage to unmerge a packages together with all the dependencies it installed (preferably with some way to choose). Unmerging has some flaws anyway, since there is no dependency check whatsoever and it is relatively easy to break your system unmerging critical packages... ok, there is revdep-rebuild, but still it would be nice to have some way of checking deps before unmerging a package...
</OT>

Anyway, the split ebuilds work great, I emerged KDE 3.4-beta1 two days ago and everything went smoothly except for some minor bugs that are already fixed by now (well, that's the price to pay for testing development versions ;-)

). Thanks to Dan and the rest for all the work, it is very much appreciated!

WladyX · Guru Joined: 25 Nov 2004 Posts: 503 Location: Romania

For your OT: I definetly agree, i also have the same opinion, but it must be an OPTION, it should not be "by default" to remove the dependencies as well.
_________________
We are not alone.

MasterX · Veteran Joined: 26 Jun 2003 Posts: 1165

I like the idea of having one ebuild for a program. Before, I had to use the DO_NOT_COMPILE option because I did not want to install some programs. But, the problem is now that I do not know which subprograms I need to install. For example, I see that there are 18 different ebuilds for Kate. I am just wondering which ones do I need to install? Why did you make 18 ebuild for a single program? Would not it be better if we had one ebuild for Kate (one ebuild for each program).
Now we have one ebuild for each subprogram.
I believe this means extra work for the developers and it will drive us crazy.
Maybe a good idea would be to have a Kate-meta ebuild for the novice users.

WladyX · Guru Joined: 25 Nov 2004 Posts: 503 Location: Romania

I agree, they should be split, but not that much or we will end up with package-devel, lib-package, package-something (like the RPM, based distros (no flame, just my subjective opinion)). One thing that made my choose Gentoo was that that compiling a package you had the whole package, not just a part of it.
_________________
We are not alone.

Gaspode · n00b Joined: 02 Oct 2004 Posts: 36

Well, that's what dependencies are for. When I installed KDE 3.4-beta1 recently, I went through the list, adding the programs I need to the 'emerge' command line, and the necessary dependencies (in particular the various lib* packages) where pulled in automatically. As for the kate ebuilds, I think the additional packages just add some submodules, and that's a good thing. I don't edit python files, so why would I want the kpybrowser module? Similarly, I never use konqueror's sidebar. So I left out konqueror-sidebar. Makes the whole thing smaller and faster. In fact, KDE 3.4-beta1 installed from the split ebuilds boots considerably faster than KDE 3.3.2, even though I installed a lot of packages. Maybe the reason is just that KDE now supports some new gcc options (such as visibility=hidden), but I think that leaving out unneeded plugins and extra-libs and so on also contribute to the beta loading faster.

By the way, why are all the beta ebuilds masked? Are they (that much) less tested than the alpha1 ebuilds? I would understand masking 3.4 completely before the release, but masking the betas and leaving the alphas does not seem like the right thing to do...

MasterX · Veteran Joined: 26 Jun 2003 Posts: 1165

Gaspode,

You are right. If you do not write in python why to install the module. But you need to know what each ebuild is for and this means that the developers have to explain to the novice users what each ebuild is used for.
Moreover, having all these ebuild makes the dependency check a little harder. Take for example Kdevelop. Kdevelop can be used to program in python, but in order to do this you need to install Kate and the necessary modules. If Kdevelop's configure script allows you to install Kdevelop without python support then the developers need to include this in the ebuild. If they have not or if Kdevelop's configure script does not have this option then you have to install Kate and the proper module. So, what is the need for this ebuild if you can not avoid its installation?
Finally, how long would it take you to install the modules and how long to install Kate itself?

thought_poet · n00b Joined: 14 Dec 2004 Posts: 25

I think you may have broke freetype:
https://forums.gentoo.org/viewtopic.php?t=280310

If not then I'm sorry, but its still broken currently so it should be checked out.
_________________
- Thought Poet

jhgz1 · Posted: Sun Jan 16, 2005 4:04 am Post subject:

I really like the idea and implementation of the split ebuilds, however one thing really bothers me:
When I want, for example, to emerge all of kde-meta and am not running a ~x86 but define the packages in /etc/portage/packages.keywords (and /etc/portage/packages.unmask) then it really becomes a drag to enter several hundred apps here and there.
anybody have some cool ideas on this?
_________________
Bei Gentoo mithelfen wollen und kein Programmierer? Gentoo sucht Übersetzer, die bereit sind kontinuierlich mitzuarbeiten.

dannycool · Posted: Sun Jan 16, 2005 8:58 am Post subject:

jhgz1:
ls /usr/portage/kde-base | awk '{ print "kde-base/"$1" ~arch" }' >> /etc/portage/package.keywords

:twisted:

Gaspode · n00b Joined: 02 Oct 2004 Posts: 36

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

The split ebuilds and KDE 3.4 are very cool so far, great job!

[edit] Finally, KDE is stripped-to-the-bone, Debian-style, FAST

MasterX · Veteran Joined: 26 Jun 2003 Posts: 1165

Gaspode,

I know that in the end is going to be much better and much faster than the monolithic version of the ebuilds. I really like the idea, I do not want to install programs that I will never use them. I just believe that having ebuild for each module is going to greatly increase the amount of work for the developers.

Shan · Guru Joined: 04 Nov 2003 Posts: 558 Location: /dev/null

I'm curious to know what the easiest way to make the switch would be? I figured just a `emerge kde-meta` and then manually remove packages I don't want as I figure them out; but obviously the split packages are blocked by my currently existing install of KDE (3.4beta monolithic; at the time I installed they hadn't even masked the split ebuilds so I didn't know they were "ready").

Obviously I *could* remove my existing KDE, and then work from there but I don't want to leave my box unusable (from a graphical standpoint) for more than neccisary.

Edit: Yeah, obviously I don't have to install kde-meta, I can just install the meta package for every kde section I've actually got (since I don't use things like kde-edu and such); but is removeing my existing kde package and then installing its split-meta clone my only option for now?
_________________
{ NO -U } { STRIP }
{ TINY }

crs · Apprentice Joined: 19 Apr 2003 Posts: 188

Hello.

First question. Can i put here bugs report and questions about meta-ebuilds? If no please delete this post.

Ok. in emerge knode i get two error:
One: akregator must be merged after libkdenetwork (or libkdepim, i don't remeber now).
Two: in knode get error:

Shan · Guru Joined: 04 Nov 2003 Posts: 558 Location: /dev/null

From the errors, it looks like your kdepim archive is corrupt / incomplete / fusked; probably on the packagers end (not faulting them I imagine they've got a lot to deal with).
_________________
{ NO -U } { STRIP }
{ TINY }

crs · Apprentice Joined: 19 Apr 2003 Posts: 188

Ok, i emerge now libkmime. But here is bug i think - please add this to dependency maybe? I don;t know. Maybe will be work now.

[edit]
After merge libkmime, knode is good work. Broken dependencies? [/edit]

GentooBox · Veteran Joined: 22 Jun 2003 Posts: 1168 Location: Denmark

I've used the 3.3.2 split kde-meta ebuilds some months now, and it works flawless

This is really nice, i've waited a long time for kde split ebuilds to get into portage.
_________________
Encrypt, lock up everything and duct tape the rest

crs · Apprentice Joined: 19 Apr 2003 Posts: 188

I have one more problem. I use konqueror. I want configure in konqueror flash, but can't set plugin path. I have not there option in konqueror configure options. What i have to install to be could use flash?

cron0 · Posted: Sun Jan 16, 2005 9:40 pm Post subject:

Finally!

Thanks to all that made this possible!

Cron0

sim0nx · n00b Joined: 30 Nov 2003 Posts: 22

When i try to emerge kmail i get this error:

zerojay · Veteran Joined: 09 Aug 2003 Posts: 1033