[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Why including meta-pkgs everywhere ?
>samedi 10 octobre 2009
>On Sat, 10 Oct 2009 20:18:03 +0200
>Demelier David <demelier.david%gmail.com@localhost> wrote:
>> There is also a lot of gnome dependencies on GTK based applications, I
>> to install gimp a long time ago and I was surprised to have plenty gnome
>> dependencies such as Gconf, ORbit and even policykit. I asked on the
>> #pkgsrc@freenode and they said `Ask gnome it's their crap' by the way gimp
>> not a gnome project and is really independant of it. Because they also say
>> `provide patches' I guess we can't say anything without providing patches ?
>Set PKG_DEFAULT_OPTIONS+=-gnome in mk.conf. graphics/gimp honours this.
Not really, it still depends on policykit, gconf, orbit..
>They don't and the dependencies don't say that they do. Generally they
>only depend on kdelibs and sometimes kdebase (in the kde3 case).
>Note that "../../meta-pkgs/kde3/kde3.mk" (and kde4/kde4.mk) are not package
>dependencies, they are common makefile fragments that set things
>appropriately for building kde packages in a pkgsrc context.
Okay, true I tought the .include was the new way to make dependencies, I just
understood now thanks for the answer.
Main Index |
Thread Index |