[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Questions about splitting kdebase into a plethora of packages
From:       Lokheed <lokheed () gmail ! com>
Date:       2005-02-10 21:20:23
Message-ID: 420BD017.3080503 () gmail ! com
[Download RAW message or body]

A better way would have been to create your own ebuild and modify it to 
install into /opt/. Using inject is by no means an alternative to making 
proper ebuilds. Besides this way is not supported at all, so you are on 
your own if you come into problem with your install.

Jason Keirstead wrote:

>On Thursday 10 February 2005 1:00 pm, Lokheed wrote:
>  
>
>>Thanks will do some reading. Thats an even worse worry now that if I do
>>come across a bug, I dont get support from KDE and will have to rely on
>>Gentoo alone as they will only support the split version because
>>apparently its too hard to maintain ONE extra ebuild but not enough work
>>to maintain 300+...I think I missed a meeting somewhere ;)
>>    
>>
>
>I use Gentoo, but do not use the gentoo ebuilds. I just maintain my own KDE 
>tree in /opt/kde.
>
>It is very easy to do this in gentoo. If you then later want to emerge another 
>app with a KDE component in the USE flag ( such as USE=arts ), just *tell* 
>portage that it is installed by using 'emerge --inject 
>kde-<whatever>/<appName>'
>
>That, and make an /etc/env.d/99kde-env entry for KDEDIRS, and you are all set.
>
>Gentoo is flexable, if you don't like the way they are packaging stuff, just 
>build your own :P
>
>  
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]