Re: PPC SHA-1 Updates in "pu"

From: Junio C Hamano <junkio@cox.net>
Date: Jun 25, 2006, 03:57 UTC
Message-ID: <7vfyhtopjm.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060625012435.GZ21864@pasky.or.cz>

Petr Baudis <pasky@suse.cz> writes:

Show 5 quoted lines

>>  - RPM target -- we probably acquired a new build-dependency in
>>    which case the .spec file needs to be updated;
>
> Well, perl is currently not listed even as a runtime dependency,
> so does it really need to be listed as a build dependency?

Really? I think rpmbuild is getting anything that matches "^use " and listing the perl modules as dependencies.

Show 5 quoted lines

>>  - Make sure Git.xs builds and installed result works fine on
>>    all platforms we care about, including Cygwin and other
>>    non-Linux boxes.
>
> Unfortunately I don't have access to a lot of those. :-(

I don't either. That's why I would want to place something low-impact on "next" to ask help from the users.

Show 20 quoted lines

>> I'd even suggest we revert the changes to git-fmt-merge-msg to
>> keep it working for now, until the above worries are resolved.
>> Otherwise we cannot have it in "next" safely (and I REALLY _do_
>> want to have Git.pm infrastructure in "next" soonish).
>
> Yes, that sounds reasonable.
>
>> We can start using Git.xs and friends in some _new_ ancillary
>> programs, once we solve building and installing problems for
>> everybody.  That way it would help us gain portability and
>> confidence without disrupting existing users.
>
> Well, I don't think it's very likely that Git.pm per se would be buggy
> on a certain specific platform - it should either work as well as
> everywhere else or not build at all, in which case you have disrupted
> the existing users anyway. :-) (But without disrupting anyone we won't
> get any bugreports and never get it fixed.)
>
> Perhaps other converted perl scripts can linger at least on the pu
> branch?

My preference is to keep your other conversion in "later" mailbox, not even in "pu", to keep them from distracting me. I'd like to have something low-impact (e.g. "git-mv" which I do not use and I do not think Linus uses) along with the perl/ directory and build procedure in "next" soonish to make sure at least things build and correctly install for everybody (compiling and linking alone would not count as "correctly install" while we have something like INSTALLSITEARCH gotcha). After we are reasonably confident about the whole .xs stuff we can revert the revert of git-fmt-merge-msg.