Message: previous - next
Month: February 2014

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

From: Michele Calgaro <michele.calgaro@...>
Date: Sun, 16 Feb 2014 04:10:50 +0000 (GMT)
>>filelight-l10n package is completely unnecessary.
>>In my build script I omit building this package.
>I don't build the package either --- duplicate of filelight.
>Why don't we purge the sources?
>Also applications/kuickshow, which is an exact duplicate of tdegraphics/kuickshow?
>And mlt/mlt++, which nothing in Trinity uses, and is horribly outdated from upstream?

Slavek, Darrell, sorry for the late reply, I am having 10 very busy days :(
I have started a new full build, which should be ready by tomorrow if there aren't any FTBFS on the major packages. After that I will test again and let you know if there are other problems.

I agree with Darrell suggestion: if there are packages that are no longer needed, why don't we purge them from the git repo? If we ever need them in the future, we can always "git checkout" them.

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).

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.