Message: previous - next
Month: February 2014

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

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 16 Feb 2014 01:51:15 -0600
On 02/15/2014 11:11 PM, Michele Calgaro wrote:
> Yes, some of the mentioned packages may be required for building older TDE
> versions (such as 3.5.13), but we have tags and as I already said

Tags are NOT a sufficient safeguard for removing directories from the
development tree if they are needed by anyone. Attempting to use tags and
introducing the requirement that developers pull multiple "tags" or "branches"
within a local repository to get needed code can completely break a local copy
causing hours upon hours to correct/rebase/clean/etc... especially with the
numerous submodules woven into the TDE git tree. In some cases requiring a
complete new clone to be pulled. (I know, I've been there)

I for one do not want to find I need a directory that has been deleted only to
have to checkout some past branch or tag to get the code to in turn find that
updates to the tree can no longer be pulled due to outstanding or conflicting
commits that cause chaos to try and sort out. There are still those building
from the tree that use the qt3/3.5.13 codebase. All of the directories
applicable to that build knetworkmanager8, etc. should remain in the tree.

As for the directories and a duplicated code or are no longer used by anyone,
let's add them to, confirm
they are safe to remove and then delete them. Thanks.

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