Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Thibaut,
my mail program seemed to eat the citations. 2nd attempt:
Am 13.04.2014 14:45, schrieb Thibaut Paumard:
> Why does the package Conflict and Replace cpl-plugin-xsh? None of
> the files are the same (so at least the Replace is wrong).
I mainly followed the rule of renaming a package.
"Replaces" is correct wrt policy:
7.6 Overwriting files and replacing packages - Replaces
Packages can declare in their control file that they should overwrite
files in certain other packages, or completely replace other packages.
The Replaces control field has these two distinct purposes.
> - are there any files in common in the two packages?
No.
> - what happens when the two packages are installed together? + are
> the two packages still usable somehow?
Yes.
> + is one package simply shadowed by the other?
On default, yes. However, they can (with python-cpl) both separately
accessed by using the version number as argument
> + is cpl completely broken in that case?
No.
> - remove the Replaces line;
That one should stay, see above.
> - replace Conflicts with Breaks or remove it altogether;
Removing the "Conflicts" field would create the special case that the
old version and the new version of the pipeline are co-installable,
what is not the case for the other recipes. This is however not a real
problem.
> - keep Provides if the new package really provides the same API;
It does. The recipes are still named as before.
> - optional: build cpl-plugin-xsh* as meta-packages that will pull
> their cpl-plugin-xshoo counterpart.
Seems a bit complicated for a popconn-zero package.
So, maybe the best would be just to remove the Conflicts field. Would
you agree?
Best
Ole
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTSpI3AAoJEHEVr9B3ENz3QMgP/i6tjIq07Xi9FzHqkcJhENhP
0j44KZ1Nb5ecgt/t9tUCBubyBa+2h6esMxseB+KJOiR+WzKmO5JlDSnv0nhFoIHH
0dMIz/L1UIwAhDnO2HJY8fmD/at0XXCqD51pt2YwHpCkUDcuqZCS5V6IWd5lckYH
DJY29ziEGwkgw1H+OxYfW8Qs8Ra0Ps9K1N9RJ6mnA7HiRBABVb0ISchhnVvzDYtn
/2jFvt9tJ2oElW4UZBy/tASXxsk+ERJYyWsDGQtaMOL5PxcnYcz4EXV9K5rVcHmV
+CS6fnyWL69KjNYFBrG10DSaM6PykqJEf1uKLfl4vCfNDdvtW4cS0zutxE+7OHpw
vkPJWJsRNAIM7DUTVNJQKW3yapi4+BsR1lT1fLOnHFQOg3AGOVqBAJNX95pZKZYB
GiDRWL79XvApmBy9jjVMIKHPz/Kor0GhYcsBNUV3vXRPisAkjbxNLXn/OvHl37FN
wt1yx48lIJFGxC+QGVR1jxNz31bZy2VEn6YBrjigtCxPLvBUw+70LMUSrME2Vo+W
7mSMLwR6TJiJ3Ve9B83WierBzYWBUQHB93YTpSCGCak08JS7QLGglUVfL5jF4gzR
MtpPmQkSKVl0GT5Tw697DnP/V0qVu8uPulUg7oM4ROZY84+36lU9sPhkux1aVLe8
rE4h9PfE3F5/uSUCQJwz
=D1xA
-----END PGP SIGNATURE-----
Reply to: