From: Tomoaki O. <ok...@so...> - 2011-01-24 18:05:09
|
At Mon, 24 Jan 2011 12:10:43 -0500, Alexander Hansen wrote: > > If you have just "A Replaces B", that means that files from A can > automatically overwrite files from B, without necessarily removing B. > This gets used a lot when files get moved around between splitoffs. > > If you have just A Conflicts B, that means that A can't be installed if > B is present. This is not automatic, and requires the user to remove B. > > If both 'A Conflicts B' and 'A Replaces B' are specified, that's the > only way that B will be automatically removed. > Thank you for the explanation. This case is surely "A Replaces B" as dmacks said. I didn't know it is possible to overwrite files that were priviously-installed. I've just committed the corrected finkinfo. To tell the truth, for an ease to maintain, I'd like to move kpathsea binaries (kpseaccess, kpsepath, ...) from texlive-base to the package "kpathsea", as splitoff in libkpathsea6.info. But if I do so, new "kpathsea" and previous texlive-base have the same binaries, and I thought it is impossible to install them simultaneously. Now I know it is possible with Replaces... Tomoaki Okayama |