On Sun, Aug 19, 2012 at 12:27:52PM +0100, Stuart Henderson wrote: > On 2012/08/18 16:42, Anil Madhavapeddy wrote: > > Are there any special considerations for renaming a port (e.g. > > security/cryptokit -> security/ocaml-cryptokit) in terms of binary upgrades > > between releases? > > > > It would seem that as long as all the dependent ports also have the new > > name, there shouldn't be, but I thought I'd check... > > > > -anil > > quick guide: > > - update any dependent ports. > > - if the path changes, you need an @pkgpath on the old path. > > - if the PKGNAME changes (other than a version increment), > you need an @conflict on the old name, an entry in devel/quirks, > and the version number of the new port must be higher than the > old one. > > - if the plist or the installed files change in any way, bump > REVISION. > > - test by building the new packages, including quirks, putting > them in a directory on their own, installing the old packages, > and running PKG_PATH=/path/to/new-pkgs/ pkg_add -u
Smaller guide: think twice. don't do it. Do you really want to rename things ? Do you really have a good reason ?
