On Fri, Jun 12, 2015 at 07:33:20PM -0700, Gerald B. Cox wrote:
I'm trying to figure out the best way to handle the situation
where a project
decides to use submodules in Git. The archive generated doesn't incorporate
the submodule files.
If upstream is generating the archive, need to ping them that their tarball
is broken. If it's an archive generated using github's automatic archiving
then the procedure you outline below is valid.
You could also make separate tarballs for the submodules but you have to get
the proper versions (so you probably end up doing a "git submodule update
--init" to do that anyway).
I've done some searching on this, and haven't really come up
I've reviewed: Packaging:Github
; but that really doesn't address the submodule issue.
I looked through some packages that are currently in the Fedora repository and
found where a few folks have rebuilt the tarball and referenced that version as
the Source in the spec file; then they put in a comment stating:
The source of this package was pulled from upstreams' vcs. Use the following
commands to generate the tarball:
- git clone
- git submodule init
- git submodule update
This approach is the best that I've found. Any other suggestions?
packaging mailing list