On 03/25/2012 02:23 PM, Darrell Anderson wrote:
> Are you discussing how to handle building both packages on Arch or proposing Tim create a new dependency package in the GIT source tree?
> 
> Darrell

Just for Arch. This is a TDE problem, but it can be addressed by packaging right
now as long a kio_svn and kio_ksvn are interchangeable (still have to test).

This IS a TDE problem though that will need to be fixed. We can't have two
independent TDE packages (tdesvn and tdesdk) that produce the same five files:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

I looked at bit at the tdesvn code (kiosvn.cpp) and it doesn't look like too
much of a problem to fix internally. I think the proper long-term solution IS to
split the packages in TDE to create something like 'tde-kiosvn' since we have
two packages that require the same capabilities.

It looks like the reason we currently have tdesvn producing what are effectively
duplicate protocol files in its build was from some earlier attempt to get rid
of the file conflicts with tdesdk in the first place:

/opt/trinity/share/services/ksvn+file.protocol
/opt/trinity/share/services/ksvn+http.protocol
/opt/trinity/share/services/ksvn+https.protocol
/opt/trinity/share/services/ksvn+ssh.protocol
/opt/trinity/share/services/ksvn.protocol
/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

I'll have to confirm further, but initially it looks like the svn+*.protocol
should have been dropped when the ksvn+*.protocol files were added to begin
with. Now those files essentially duplicate each other.

Checking my opensuse 3.5.10 install, svn+*.protocol is provided by kdesvn while
kdesdk provides NO .protocol files at all.

Another way to do this is just to make tdesvn a dependency of tdesdk and drop
the protocol files from tdesdk altogether. (I like that idea) No split package
and the tdesvn overhead is small:

1848392 Mar 25 13:44 tde-tdesvn-3513_tqt-2-x86_64.pkg.tar.xz

1.8M - no biggie.

What do you think? Which option do you like the best?

(1) create a 3rd package with the common files to prevent conflict.
(2) simply drop the .protocol files from tdesdk and making tdesvn a dependency
of tdesdk.


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