[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] wget-1.16.1.46-3d8e7 missing hint in the tarball
From: |
Darshit Shah |
Subject: |
Re: [Bug-wget] wget-1.16.1.46-3d8e7 missing hint in the tarball |
Date: |
Mon, 23 Feb 2015 20:55:43 +0530 |
Not really. Because README.checkout contains information that would be
confusing to the average user who downloads a tarball. README.checkout
should contain specific information that is required by those who
clone the git repositories. It needs to enumerate the additional steps
like `git submodule init; ./bootstrap', etc. And the additional
libraries that the system requires. I think the two files need to be
separate.
But yes, the part about running the test suite belongs to README and
not README.checkout
On Mon, Feb 23, 2015 at 8:49 PM, Giuseppe Scrivano <address@hidden> wrote:
> Tim Rühsen <address@hidden> writes:
>
>> Hi Darshit,
>>
>> Am Mittwoch, 18. Februar 2015, 22:39:18 schrieb Darshit Shah:
>>> Readme.checkout is a file that is only available in the git
>>> repository. I guess this is a side effect of having
>>> gitlog-to-changelog generate out changelogs. A reference to this file
>>> has crept into the tarball.
>>>
>>> libio-socket-ssl-perl is required only for running the test suite and
>>> hence it not included in the README for the tarball.
>>
>> AFAICS, the test suite is included in the tarball, isn't it ?
>>
>> So there is no reason to not run the test suite after compiling.
>> To do so, there should be a list of needed software packages (anyway needed
>> for compiling).
>>
>> What about renaming README.checkout to README + small amendments to the text
>> to distinguish between compiling from tarball and git ?
>>
>> What do you think ?
>
> Good idea. I think we could just append README.checkout to README as it
> is now and drop README.checkout.
>
> Regards,
> Giuseppe
>
>
>
--
Thanking You,
Darshit Shah