Joey Hess wrote:
> Muharem Hrnjadovic wrote:
>> sorry for not responding earlier. What would be the best way to perform
>> the suggested full-archive test?
>
> * Clone pristine-tar git repo.
> * git checkout origin/testsuite
> * Use the testexternal target in the Makefile, which expects you to
>
Joey Hess wrote:
> Muharem Hrnjadovic wrote:
>> sorry for not responding earlier. What would be the best way to perform
>> the suggested full-archive test?
>
> * Clone pristine-tar git repo.
> * git checkout origin/testsuite
> * Use the testexternal target in the Makefile, which expects you to
>
Joey Hess wrote:
> Muharem Hrnjadovic wrote:
>> sorry for not responding earlier. What would be the best way to perform
>> the suggested full-archive test?
>
> * Clone pristine-tar git repo.
> * git checkout origin/testsuite
> * Use the testexternal target in the Makefile, which expects you to
>
Muharem Hrnjadovic wrote:
> sorry for not responding earlier. What would be the best way to perform
> the suggested full-archive test?
* Clone pristine-tar git repo.
* git checkout origin/testsuite
* Use the testexternal target in the Makefile, which expects you to
provide it with `tars` file li
Muharem Hrnjadovic wrote:
> Joey Hess wrote:
>> Muharem Hrnjadovic wrote:
Also, the
tar-generated manifest sometimes contains filenames encoded in ways that
pristine-tar does not understand, but tar does, and your patch would
certianly fail then.
>>> Could you please provide mor
Joey Hess wrote:
> Muharem Hrnjadovic wrote:
>>> Also, the
>>> tar-generated manifest sometimes contains filenames encoded in ways that
>>> pristine-tar does not understand, but tar does, and your patch would
>>> certianly fail then.
>> Could you please provide more detail on this. This is somethin
Joey Hess wrote:
> Muharem Hrnjadovic wrote:
>>> Also, the
>>> tar-generated manifest sometimes contains filenames encoded in ways that
>>> pristine-tar does not understand, but tar does, and your patch would
>>> certianly fail then.
>> Could you please provide more detail on this. This is somethin
Muharem Hrnjadovic wrote:
> > Also, the
> > tar-generated manifest sometimes contains filenames encoded in ways that
> > pristine-tar does not understand, but tar does, and your patch would
> > certianly fail then.
>
> Could you please provide more detail on this. This is something I'd like
> to a
Joey Hess wrote:
> Muharem Hrnjadovic wrote:
> > pristine-tar's "gendelta" command does not check whether all paths in
> > the manifest are also present in the local/unpacked source tree.
> Nor should it; pristine-tar gendelta can be run from anywhere; it has
> no knowledge about the source tree t
9 matches
Mail list logo
