trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] Commit c926c513 (amarok) caused a conflict between packages

From: "David C. Rankin" <drankinatty@...>
Date: Sat, 15 Feb 2014 22:40:32 -0600
On 02/15/2014 10:10 PM, Michele Calgaro wrote:
> In addition to filelight-l10n (which I don't use too, even though I haven
> been building it), applications/kuickshow and mlt/mlt++, I am also thinking
> about knetworkmanager8 and kpowersave. AFAIK, they have been replaced by
> tdenetworkmanager and tdepowersave and I don't use them anymore
> (knetworkmanager8 also FTBFS).
> 
> Slavek, in the git packaging repo, under Ubuntu there are a lot of folders.
> Are they all necessary or can we purge some? I am thinking about
> lucid_automake and maverick_automake, plus the 'kdegraphics.automake' and
> 'kdevelop.cmake' that are in almost all Ubuntu distros. There may be some
> more, but in general I wonder if we can do a little of clean-up. Debian
> distros packaging folders are much cleaner IMO.

Let's not throw the baby out with the bathwater. kuickshow can go as it is
duplicated in tdegraphics or one of the others. mlt/mtt++ do have dependency
value (I forget which package, but I chased that dependency down 2 or 3 years
ago and it was still worth keeping even being i686 only).

If I recall correctly knetworkmanager8 AND kpowersave ARE required for QT3
3.5.13 builds. Let make sure our decisions are technically correct and not
simply based on whether anyone chooses to build them anymore.

What I would like to know is "What in the heck are 'l10n' packages anyway?"

-- 
David C. Rankin, J.D.,P.E.