develooper Front page | perl.perl5.porters | Postings from January 2009

Re: Minimal Perl git repostory

Thread Previous | Thread Next
January 7, 2009 11:55
Re: Minimal Perl git repostory
Message ID:
2009/1/7 Jerry D. Hedden <>:
> Jerry D. Hedden wrote:
>> Building Perl inside a git repository is necessary so that
>> the git commands in (and elsewhere) will
>> work.
> demerphq wrote:
>> Not true. Its totally possible to build perl without git at all.
> I didn't mean that git was necessary to build Perl.  I meant that
> I wanted to be able to build in such a way that the git commands
> used by still work.
>> You didnt really think I made it necessary to have git
>> around to build did you?
> No, I did see the .patch stuff, but I'm not using the rsync
> method.
>> Anyway, have you tried rsyncing from the APC? Notice anything
>> different about it?
> I'm gonna still with the git method for now.
>> Assuming you have perl already installed:
>> git pull # whatever, update git.
>> perl
>> git archive --format=zip HEAD > $zips/
>> zip $zips/ lib/ git_version.h
> This is for the head of the blead branch, right?
> How about for some particular commit ID?
>    git pull
>    git checkout COMMIT_ID
>    perl
>    git archive --format=zip COMMIT_ID > $zips/
>    zip $zips/ lib/ git_version.h
>    git clean -dxf              # Clean up
>    git checkout blead          # Return to default branch

It takes a "treeish" as an argument, which includes "commitish".

So yes.

I still dont see why you do it like this. It seems a pity to not know
what branch the commit is on, for what seems to me to be no good

perl -Mre=debug -e "/just|another|perl|hacker/"

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About