ndmanager: Make port obsolete

[NicosPavlov]

In the process of making KDE3 obsolete in MacPorts, the Portfile ndmanager should be marked as obsolete and replaced by its more recent version based on KDE4, ndmanager2. Please see the attached patch.

[FlorianFranzen@…]

I don't really see the reason why we even have a ndmanager2 port. The new version of ndmanager does not introduce any new features or incompatibilities between versions. or saved files. I don't think a change in dependencies from qt3 to qt4 really justifies a new portsfile. Just to emphasize my point: Macports is the only package manager that offers a ndmanager2 package.

Can we not just go ahead and rename ndmanger2 to ndmanager instead?

[NicosPavlov]

I agree that a simple upgrade could be ideal, but the issue is in the dependencies. Qt3 and qt4-mac are conflicting, so that they cannot be installed together. A simple upgrade of the port would therefore not work directly because of the conflict. The separate ports are meant to provide a smoother transition, and to inform users of the consequences of the upgrade, as they may lose other programs in the process.

[NicosPavlov]

With the purpose of not breaking users' installation, is the solution proposed above acceptable, or is there another approach I am not aware of which could achieve the same purpose?

Ndmanager is one of the last port clinging to kdebase3, so that I would be keen on being able to take care of it, to clean up kde3 for good.

[neverpanic (Clemens Lang)]

This might be a use case for the so-called deactivate hack. Note that the hack would have to be added to the port that actually conflicts with qt3, which would be qt4-mac. I'm not sure that's what we want.

I agree keeping around a qt3 version of ndmanager is pointless though.

[FlorianFranzen@…]

Ok, I see the problem now. I guess introducing "ndamanager2" is indeed the easiest way out.

I guess there is now way for us to rename ndmanger2 to ndamanger at a later point either without causing conflicts for the people that have not updated in a while.

I am just wondering what kind of plans you have after removing kde3 and as a consequence ndmanager from macports for ports like this. Would we just stick with ndmanger2 then?

[NicosPavlov]

I don't really want to force changes on qt4-mac, a port which is complicated enough as is. Furthermore, there is also a dependency to kde3, so that another deactivate hack would have to be used, added to the fact that this would imply automatic deactivation, which could break other ports.

Replying to FlorianFranzen@…:

I guess there is now way for us to rename ndmanger2 to ndamanger at a later point either without causing conflicts for the people that have not updated in a while.

I am just wondering what kind of plans you have after removing kde3 and as a consequence ndmanager from macports for ports like this. Would we just stick with ndmanger2 then?

As you said, there could always be a conflict for people who did not update. For this reason, there a policy in Macports that after one year ports can be removed. We could therefore stick with ndmanager2 for now on, or possibly rename back ndmanager after some time, even though this would imply a transfer by users again.

Since there seem to be an agreement on the approach, I will commit the change shortly.

[NicosPavlov]

Committed in r126183.