From: Keith M. <kei...@us...> - 2013-09-03 18:59:37
|
On 02/09/13 23:08, Earnie Boyd wrote: > And I guess I should be doing the rest such libraries? Yes. Anywhere you've moved content from one logical package container to another, you've introduced a potential conflict. To circumvent this you need to declare a requirement, to ensure the the original container is upgraded to a state where it no longer provides the conflicting content. > Frankly, I like 999.999 indicating end-of-line but I think I'll not > do it for now and wait on your better solution of <replaces ... />. That may be okay, provided you don't mean that you won't do *anything* right now. You have introduced a conflict with an immediate impact; it requires an immediate resolution, and I have no idea when I may get around to implementing "<replaces ... />". Right now, the only option available to you is to upgrade the old package, with a <requires ... /> dependency, to remove the conflict. -- Regards, Keith. |