Ticket #552 (closed defect: invalid)
Conflict files with kdesdk
| Reported by: | explinux@… | Owned by: | alwin |
|---|---|---|---|
| Priority: | normal | Milestone: | not applicable |
| Component: | All | Version: | 1.2.x |
| Severity: | tweak | Keywords: | not a bug |
| Cc: |
Description (last modified by alwin) (diff)
Hi in my distribution Archlinux, your application is in conflict with kdesdk package. These files are in conflict:
/usr/share/kde4/services/svn+file.protocol /usr/share/kde4/services/svn+http.protocol /usr/share/kde4/services/svn+https.protocol /usr/share/kde4/services/svn+ssh.protocol /usr/share/kde4/services/svn.protocol
these files of the kdesdk package are the same as yours? Excuse for my english. Very Thanks
Attachments
Change History
comment:1 Changed 5 years ago by alwin
- Keywords not a bug added
- Status changed from new to closed
- Resolution set to invalid
comment:2 follow-up: ↓ 3 Changed 4 years ago by anonymous
But then that other package (the one with the svn+xxx files) will still conflict with kdesdk, so what is the real solution here?
And what happens if the user has ksvn+xxx protocols from kdesvn, but svn+xxx from kdesdk?
A few lines in the README file regarding this issue wouldn't make any harm. Also, a cmake option to disable the kio protocols from building at all would be nice.
comment:3 in reply to: ↑ 2 Changed 4 years ago by alwin
- Description modified (diff)
Replying to anonymous:
But then that other package (the one with the svn+xxx files) will still conflict with kdesdk, so what is the real solution here?
And what happens if the user has ksvn+xxx protocols from kdesvn, but svn+xxx from kdesdk?
When kde programs using svn+xxx from kdesdk than it uses the base subversion of kdesdk. No problem. Does not conflict with kdesvn.
A few lines in the README file regarding this issue wouldn't make any harm.
I put something into INSTALL
Also, a cmake option to disable the kio protocols from building at all would be nice.
Them will not build, these are files within kdesvn source. In my packages I build for fedora them are not inside base installer but an extra package. What other packagers does - don't know. Debian packages are seperated as far as I know, too.
comment:4 follow-up: ↓ 5 Changed 4 years ago by anonymous
I put something into INSTALL
I don't know what you are talking about, in the INSTALL-cmake file there is nothing about it, and I don't see any other INSTALL file.
Them will not build, these are files within kdesvn source. In my packages I build for fedora them are not inside base installer but an extra package. What other packagers does - don't know. Debian packages are seperated as far as I know, too.
So basically you didn't make decision on this issue, so you leave the decision to be taken by each packager. In my case, without knowing any better, I would think that removing the protocol files from the kdesvn package is the proper way of action, and there is no point on releasing additional packages with these files, because there will always be a conflict.
Notice that probably every user of kdesvn will also have kdesdk installed.
So in conclusion, I think its better to have it solved by upstream than by packagers.
comment:5 in reply to: ↑ 4 Changed 4 years ago by alwin
Replying to anonymous:
I don't know what you are talking about, in the INSTALL-cmake file there is nothing about it, and I don't see any other INSTALL file.
Wrong words: I'll put something - it isn't done yet. Btw. in handbook is a comment about that.
So basically you didn't make decision on this issue, so you leave the decision to be taken by each packager. In my case, without knowing any better, I would think that removing the protocol files from the kdesvn package is the proper way of action, and there is no point on releasing additional packages with these files, because there will always be a conflict.
Feel free removing it. Thats the reason I setup that alternative ksvn+xxx, too. For those not having protocols from kdesdk the svn+xxx by kdesvn are installed.
Notice that probably every user of kdesvn will also have kdesdk installed.
So in conclusion, I think its better to have it solved by upstream than by packagers.
What should I solve? There is no bug. It is the descicion of every user or packager which kind of protocol implementation them want to use. This is the desciscion of every distribution, how to handle such conflicts. On Debian the svn protocol implementation of kdesdk are extra packages. Fedora not, but there the protocols from kdesvn are moved out. So what. The only solution I would have were deleting my implementation. Why should I do that? 'Cause package builders aren't willing checking for possible conflicts and mark them per package?
Packagers will install not direct into system. Them are installed into seperate folders than packed. And my packed into different files. So it is THEIR descicion what to do. After "make install" job of kdesvn build system is done. And if Archlinux isn't able splitting it - sorry.
Feel free telling them. Feel free giving this bug report. But what OpenSuse?, Fedora, Ubuntu, Debian, Gentoo are able Archlinux should be able, too. If they want having some help by me - why not.
but I'll not remove my protocol implementations of svn+xxx.
no are not same, kdesdk has an own simple svn filesystem.
thats why most distributions put the svn+xxxx - files of kdesvn into an extra package so them don't conflict with kdesdk when installing kdesvn and kdesvn has "ksvn+xxx" protocols (eg. ksvn+http://... and so on)