vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, I have a question in regards to the new kde split ebuilds. Currently I am using the kde meta-ebuild to install kde 3.3. In the future will I be able to use the kde meta-ebuild to install all kde components then manually un-merge specific components using application specific split ebuilds? I prefer installing everything then uninstalling what I don't want. |
| ||||
| In article <114use8kf7hub0c@corp.supernews.com>, Kyle Peterson <kpeterson@hermies.net> wrote: > Hello, I have a question in regards to the new kde split ebuilds. > Currently I am using the kde meta-ebuild to install kde 3.3. In the > future will I be able to use the kde meta-ebuild to install all kde > components then manually un-merge specific components using application > specific split ebuilds? I prefer installing everything then > uninstalling what I don't want. Theoretically, yes. Quite how this will work in practice remains to be seen. I can see one problem area. Suppose you only want KMail but not KNode from what is currently kdepim (kdepim-meta for the 3.4 split ebuilds). If you merge kdepim then unmerge knode you might find that emerge wants to re-merge KNode all the time. You may have to unmerge the meta packages and possibly add the packages you want to keep to the world file to keep things consistent. This is academic really though. I haven't tried the split ebuilds yet (I'm waiting until I absolutely have to) so I don't know for definite what will happen. I suppose it's a suck it and see situation. -- Andy. |