Skip to Content.
Sympa Menu

perfsonar-dev - Transition to new naming policy

Subject: perfsonar development work

List archive

Transition to new naming policy


Chronological Thread 
  • From: Błażej Pietrzak <>
  • To: GN3 SA2 t3 <>,
  • Subject: Transition to new naming policy
  • Date: Fri, 03 Jul 2009 12:57:54 +0200

Hello all,

Since the official package naming policy has changed the old packages have to change their names.
The problem lies with package upgrading. If the name of the package changes the package management software does not remove the previous package.

In order to solve the problem for DEB packages one has to add two properties in the control file describing the package: "Conflicts" and "Replaces", both with the previous name of the package. So for example for "perfsonar-java-sshtelnet-mp" package one has to add:

Conflicts: ps-mdm-sshtelnet-mp
Replaces: ps-mdm-sshtelnet-mp

This will inform the package manager that it should remove the "ps-mdm-sshtelnet-mp" package from the system and then install "perfsonar-java-sshtelnet-mp" package.
If one would introduce only "Replaces" property then it will tell the package manager that the "perfsonar-java-sshtelnet-mp" package can override files of the "ps-mdm-sshtelnet-mp" package, so that is why one also has to add "Conflicts" property.

Unfortunately there is no such mechanism for the RPM packages. In case of RPM packages one has to create a dummy package with the previous name that has dependency for the package with new name.

Best regards
Blazej



Archive powered by MHonArc 2.6.16.

Top of Page