Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverted to commit ca62a2d66. #5

Open
wants to merge 1 commit into
base: devel
Choose a base branch
from
Open

Reverted to commit ca62a2d66. #5

wants to merge 1 commit into from

Conversation

hakonhagland
Copy link

Let dzil generate/modify the files of the distribution.

Commit 94d5a6e added files that should be generated by dzil build. This commit deletes the files added and restores files which was modified. The files are reverted to the version in commit ca62a2d.

Now, this introduces a small problem of how to include the last commit c2ca1e9. This commit was added after 94d5a6e and modifies the README file slightly. However the README file is currently generated by dzil build by plugin [Readme]. Some options to handle this is:

  • Remove the [Readme] plugin such that the README file is not generated. This has a disadvantage that the README file must be updated manually if the copyright year or version of the module changes, or
  • write a custom plugin that modifies the generated README (after it has been generated but still during the dzil build), or
  • use another plugin like [ReadmeAnyFromPod], or
  • put the added information in some other file, or
  • abandon the added infomration all together.

Let dzil build the files of the distribution.

Commit 94d5a6e added files that should be generated by "dzil build".
This commit deletes files added, and restores files which was modified
to the version in commit ca62a2d.

A small problem that this commit introduces is how to include the last
commit c2ca1e9 ?
This commit was added after 94d5a6e and modifies the README file.
However the README file is currently generated by "dzil build" by plugin
[Readme]. Some options to handle this is a) to remove the [Readme] plugin,
such that the Readme file is not genereated. But this has a disadvantage
that the README must be updated manually if the Copyright year or
version of the module changes, b) write a custom plugin that modifies
the generated README, c) use another plugin like [ReadmeAnyFromPod], d)
put the added information in some other file, e) abandon the added
infomration all together.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant