Conversation
Member
Author
|
We also have to keep the manual |
Member
|
Not entirely sure it's a good idea to do this. Dogfooding can help against breaking stuff. Either way, I released a Substitute plugin for dzil, that should make the rewriting of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'd like to use
Dist::Zillato manage the dist.There are still several things to fix before we pull this in, mostly custom stuff we do during packaging:
<remove_me>stuff inBuild.PLMANIFESTis really the sameMETA.jsonMETA.ymlcontains what it's supposed to contain=item <autogenerated_accessors>inlib/Module/Build/API.pod<action_list>inlib/Module/Build.pmPOD$VERSIONinlib/Module/Build/Base.pmautomatically, omitting it causes a compile error when we use$VERSIONlater in the code.