Hey, I want to remove the support for "in memory assets" from Mojolicious::Plugin::AssetPack.
The reason I implemented it in the first place was to support building assets for an application that was installed in a read-only directory. This again meant that if the checksum logic or something else changed, the application would fail to start up since it has nowhere to save the files. My plan forward now is that instead of supporting this, I want to be able to freeze the asset name to output files so the process logic won't be called, but using the mapping produced while developing the application instead. This change will also remove a lot of lines of code and release a complexity I don't really want to maintain. So... Is anyone using "in memory assets" functionality? If so, how long before I can remove it? I do think no-one is actually aware of this functionality, so I might just remove it without a warning even if it's not documented as EXPERIMENTAL. Best regards, Jan Henning Thorsen, aka batman -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious+unsubscr...@googlegroups.com. To post to this group, send email to mojolicious@googlegroups.com. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
