Justin Pryzby wrote: > On Mon, Jan 29, 2007 at 10:00:13PM +0800, Thomas Goirand wrote: >> Package: package1 >> Replaces: package2 >> [...] >> >> Package: package2 >> Replaces: package1 >> >> The only thing that differs from both packages are dependencies, nothing >> else. > You said there is also a Provides? > >>> Can the user choose to install package1 and package2 on the same system >>> or have you got a Conflict: setup? >> They Replaces: each other. > It isn't clear to me that your use of Replaces makes sense. Note that if you > don't also have a Conflicts, this just means that it is not an error that > package 1 and 2 contain the same pathname; the file on disk will be whatever > is > included by the the more-recently installed package, and the other package > will > no longer be recorded as an "owner" of that file. The packages will be > co-installable. > > Justin
I don't want that it's possible to have them both at the same time. Once again, my package1 and package2 are the same, only dependencies are not. So can I write: Package: package1 Conflicts: package2 Replaces: package2 [...] Package: package2 Conflicts: package1 Replaces: package1 Provides: package1 Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
