Re: mrtrix3 is "coming". Howto tests?
On Thu, 06 Sep 2018, Andreas Tille wrote:
> On Wed, Sep 05, 2018 at 04:12:55PM -0400, Yaroslav Halchenko wrote:
> > > I know there is some way to create pristine-tar from plain Git packaging.
> > > I'd be really happy if you would consider this since it enables other
> > > team members to rebuild the package with the workflow described in team
> > > policy.
> > I do not think pristine-tar would work with git submodules, thus
> > requiring a delta of the size of the testing/data .
> Pristine-tar has nothing to do with the structure of the git repository.
$> grep ls-tree /usr/bin/pristine-tar
"git ls-tree -r --full-name $branch | git update-index --index-info");
open(LIST, "git ls-tree $b --name-only | sort -Vr |");
...
(git)hopa:~exppsy/mrtrix3[debian]git
$> du -scm .git/objects
26 .git/objects
26 total
$> pristine-tar commit ../build-area/mrtrix3_3.0\~rc3+git86-g4b523b413.orig.tar.gz master
warning: pristine-gz cannot reproduce build of ../build-area/mrtrix3_3.0~rc3+git86-g4b523b413.orig.tar.gz; storing 96% size diff in delta (16653927 bytes)
(Please consider filing a bug report so the delta size can be improved.)
pristine-tar: committed mrtrix3_3.0~rc3+git86-g4b523b413.orig.tar.gz.delta to branch pristine-tar
pristine-tar commit master 59.63s user 1.09s system 102% cpu 59.043 total
$> du -scm .git/objects
56 .git/objects
56 total
> It just stores metainformation of the orig.tar.gz you produced in a
> separate branch to enable gbp recreating a byte-identical tarball as you
> used to upload.
to recreate it from git tree. Without awareness of submodules, it would need
to keep the delta for the entire submodule tree. Not sure if that is worth to
breed across commits, since it would just keep adding those 16MB with every
pristine-tar commit
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
Reply to: