Will .patch exist in a released Perl? (Re: Revised git related information in -v/-V output (and %Config))

On Tue, Dec 30, 2008 at 7:11 PM, demerphq <demerphq@gmail.com> wrote:

> When built within  a git repository git is queried directly. When built from a
> snapshot or bundle it is assumed that the source is unchanged, and that
> the required details are avaialble in a file called .patch

What happens when building from a release tarball?  Will generating
the .patch file become part of cutting a release?  If not, it looks
like the build will fail because make_patchnum.sh tests for .patch and
otherwise uses git.  Apologies if this scenario has been covered some
way I'm not seeing.

• Will .patch exist in a released Perl? (Re: Revised git related information in -v/-V output (and %Config)) by Craig A. Berry
• Re: Will .patch exist in a released Perl? (Re: Revised git related information in -v/-V output (and %Config)) by demerphq
• Re: Will .patch exist in a released Perl? (Re: Revised git related information in -v/-V output (and %Config)) by Craig A. Berry
• Re: Will .patch exist in a released Perl? (Re: Revised git relatedinformation in -v/-V output (and %Config)) by H.Merijn Brand
• Re: Will .patch exist in a released Perl? (Re: Revised git related information in -v/-V output (and %Config)) by demerphq
• Re: Will .patch exist in a released Perl? (Re: Revised git relatedinformation in -v/-V output (and %Config)) by H.Merijn Brand
• Re: Will .patch exist in a released Perl? (Re: Revised git related information in -v/-V output (and %Config)) by Yitzchak Scott-Thoennes
• Re: Will .patch exist in a released Perl? (Re: Revised git related information in -v/-V output (and %Config)) by demerphq