Hi Jan,
Jan Pazdziora wrote:
Hello John,
I generally wonder how correct it is to have the tarballs of this size
there. Especially looking at its name, it looks like some kind of
nightly build. So I assume it will get replaced eventually, and by
having it as tar.gz in there, the next check-in will again bring in
the whole 70 MB beast because git will not have a way of storing it
as a diff or sharing content of common files from those tarballs.
Maybe we shouldn't store such things in git at all and just change the
make test-srpm / make srpm targets to download the Source0 thing from
the remote URL?
I understand your concern, I felt uncomfortable committing this file,
yet wasn't aware of a better place to store it. I'm worried about the
longevity of nightly builds from nutch's hudson, I would think they
won't be available for long. That's my only argument against making a
script fetch this when it's required. Do we have any place we can store
a tarball, so I don't need to pollute git with this?
Or maybe we'd want to unpack that tar.gz, so that subsequent changes
can only store the diff?
This is possible, but might create a little more work as nutch includes
3rd party jars in the tarball, the extra work required would be to
ensure after upgrading to a new version, that any older jars hanging
around get removed.
The end goal is to get nutch into Fedora.
This wiki page outlines the packaging needed:
https://fedorahosted.org/spacewalk/wiki/GettingPackagesIntoFedora/Nutch
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
