You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I installed and ran Serge, config_schema.serge is missing causing serge localize to error out. It appears it's not included when installing the module with ./Build install. I also noticed *schema.sql files.
I think the correct way to handle this would be to use share_dir in Build.PL and File::ShareDir.
Are you ok with using File::ShareDir? If so I'll try to put together a pull request.
I haven't forgotten about the tweaks to parse_csv or vcs_p4, but I'm trying to get Serge deployed here before I go back and work on those, hence this issue.
The text was updated successfully, but these errors were encountered:
I think File::ShareDir is the 'proper' way to do this, but when I've used it before it has an unfriendly kink. You must run ./Build and run the program from blib for File::ShareDir to pick up your files. You can't run directly from lib, which is quite common.
I see you're using FILE to get the directory, so I think a simpler method would be to simply copy the static files over using add_build_element('sql'), etc, in Build.PL. This won't require any code change outside of Build.PL and will work consistently during development and after installation.
I made a small change and I'm currently testing that. If it looks good I'll submit a pull request.
When I installed and ran Serge, config_schema.serge is missing causing
serge localize
to error out. It appears it's not included when installing the module with ./Build install. I also noticed *schema.sql files.I think the correct way to handle this would be to use
share_dir
in Build.PL and File::ShareDir.Are you ok with using File::ShareDir? If so I'll try to put together a pull request.
I haven't forgotten about the tweaks to parse_csv or vcs_p4, but I'm trying to get Serge deployed here before I go back and work on those, hence this issue.
The text was updated successfully, but these errors were encountered: