Authors CurseForge

When you pull a library defining it in pkgmeta, the packager ignores all @something verbs

This rendere, for example, useless the localization for libraries.

This was working with the old packager.

I already raised this bug but was told that behaviour was the same in old packager but this is not true. checked all zips and keyowrd substitution was managed for files pulled via pkgmeta

Are these tickets private only? Or is there some place where we can see the progress on ongoing issues?

Any update on this? LibDogTag and friends (LDT-Unit, mainly) use file date for versioning. If this isn't working, they fall back on using the development version number, which is higher than any date would ever be. This essentially breaks versioning of embedded copies of the library entirely.

Can't you put some pressure on them? This issue is quite annoying and shouldn't be that difficult to fix...

+1 for a resolution to this issue - it breaks my addon completely in-game when embedded.

i.e. 1x ...ctiveProgress\Libs\LibObjectiveProgress-1.0\LibObjectiveProgress-1.0.lua:7: unexpected symbol near '@'

I could work around it by trying to detect if the resolved symbol is a number and providing an alternative, but that is pretty crazy.

Please, raise this issue priority, it's impacting all libraries developers

Looks like tags are honored again BUT a new issue raised:

Localization tags are pulling localization from the embedding addon, not from the embedded one.

This makes localization unusable for libraries.

You can check my addon OrderHallCommander

The file libs/LibInit/LibInit.lua (pulled from LibInit) no longer ends with

--@do-not-package@
-- Packager stil not honoring this tag
--@end-do-not-package@

but when you check the file libs/LibInit/Localization.lua you see that it contains localization keys from OrderHallCommander, not from LibInit