On Sun, 28 Dec 2008, Damien Miller wrote: > > > What does that do? The files conflict already... > > > > It will prevent you from having a borked pkg install. > > I don't think that would be possible anyway since the subpackages have > an explicit dependency on the -main package, and that is where the > files have moved to.
You need to make the new -main package conflicts with the old subpackages. e.g. something like the following in lang/python/2.5/pkg/PLIST-main: @conflict python-bz2-<=2.5.2p7 > > See pkg_create(1). > > That doesn't really explain how it avoids "a borked pkg install". Without conflict, the package will start to install but stop when a file already exists and you'll end up with a partial installation. On a side note, when such big pkg move are introduced, you should really test the upgrade path. But is seems I'm the only one commenting about that stuff, so maybe I worry too much ;-) Cheers! -- Antoine
