[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:       Calvin Spealman <calvin () ironfroggy ! com>
Date:       2005-02-13 12:12:40
Message-ID: 1184327.hjAqc8mxyl () ironfroggy ! com
[Download RAW message or body]

The problem I see with this, as a Gentoo user, is that portage has far too
limited a vocabulary for describing the relationships between packages. For
example, if Konqueror is installed because I installed the kde-meta
package, being a separate package, it will not be removed when I installed
a newer version of Konqueror (assuming different directories, as Gentoo
does). Gentoo's portage system lacks such vocabulary as "this package
includes that package" and "this package is installed implicitly for those
packages", which could be used to be a little smarted about post-install
package management issues.

Simone Gotti wrote:
>> The solution seems pretty clear to me - do what debian has done for
>> years,
> and
>> make some ghost ebuilds for the kde packages (kdelibs, kdebase,
> kdenetwork,
>> etc), that contain no files themselves, but rather, depend on the other
>> ebuilds that make up the sum of that package. Thus, if you 'emerge
> kdebase',
>> you get everyting. But if all I want is Konqueror, I can just emerge
>> that.
> 
> This is what we did. It's logical...


 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]