The conflict lies in the fact that the simple name string "ps2-packer" now matches two different filesystem objects. One is the "ps2-packer.elf" file of the new instance of that package directly inside the "/bin/" folder, while the other is the "ps2-packer/" folder containing the old instance of that package, stored in "/bin/ps2-packer/".
Basically you have three options.
1: Refuse the latest change of OPL's lib usage and revert to the old.
Advantage: Simple to do
Disadvantage: your OPL source will then branch off from the standard
2: You could split your libs into two branches, to cope with the differing project needs.
Advantage: All source libs continue to follow their separate standards, both old and new.
Disadvantage: You'll have to keep switching libs back and forth a lot for different projects.
3: You could update your old projects to use the new method too, and get rid of the 'extra' package in "/bin/ps2-packer/" folder.
Advantage: All projects will follow the new standard.
Disadvantage: It will take a little extra work to adapt the other projects correctly.
But seriously, the change for older projects only consists of removing one substring component from the path string for the ps2-packer binary, so it is dead easy to do.
So this is definitely the method I'm using myself. Note also that this has no bearing at all on such projects that do not perform any elf packing as part of the makefile processing.
Best regards: dlanor