Message: previous - next
Month: December 2011

Re: [trinity-devel] Trinity Application Descriptions

From: Darrell Anderson <humanreadable@...>
Date: Tue, 27 Dec 2011 08:23:47 -0800 (PST)
> Can I suggess the following changes?
> I can then use your "topic names" as the directory for my
> build scripts 
> and your docs would match the packaging repo.
> Also the packaging directories under each distro can be
> named as your 
> topics so that the tde packaging git repo has some order to
> it.
> That way under each distro we would have for example:
> tde-packaging/arch/
>     dependencies
>     desktop
>     libraries
>     applications

Please change what you want. I threw that list into the conversation only as a starter. Something off the top off my head.

One only caveat is there is a pecking order for building some packages. Obvious is the foundation dependency packages: tqt3, tqtinterface, etc., need to be built before anything else.

PyQt3 and PyKDE3 need to be built before building kdebindings. Not required but there will be no Python integration if those packages are not built first. I think those two packages are renamed in TDE.

libical, libcaldav, and libcarddav need to be built before kdepim. The latter two are not required but must be built if kdepim is to take advantage.

Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.

I can post an exhaustive list if anybody is interested.