On Thu, Apr 21, 2011 at 09:38:03AM -0500, Amit Kulkarni wrote: > Mikolaj, > I initially just went by what the enlightenment devs renamed the > package to. What would you propose to keep the pkgname?
Smooth 'pkg_add -u' update process. Otherwise you need to add @conflict markers to the PLIST (not a big issue) and upgrade path to devel/quirks as pkg_add(8) on it's own will not be able to figure out that package name changed. From what I can see on this list quirks modifications are trying to be kept to minimum. Sometimes it's good to change pkgname if that gives a value to the user, or to the porter. For example it will be easier to find a port/package in /usr/ports or on openports.se. In this case change from enlightenment to enlightenment-e16 doesn't give any value, unless e17 will coexist with pkgname enlightenment-e17 next to e16. As I'm not involved with e16 nor e17, call is not up to me about the pkgname change. I've just asked, why are you changing the name from quirks modification and conflict marker change perspective. -- best regards q#
