"Lars Hjemli" <hjemli@xxxxxxxxx> writes: > But the buildsystem/policy used by the fedora project does not allow > network access during package builds, and since it is quite unlikely > that the git package always will match the exact release needed by the > cgit package, I only see four options: > 1) the fedora project makes a 'git-for-cgit' package containing the > needed release of the git sources > 2) the cgit release tarballs includes the needed git sources 2b) make cgit .spec use _two_ tarballs as a source, one with cgit sources, one with git sources. This assumes that you always use released git version as a base. This is immediate solution. > 3) the cgit sources are subtree-merged into git I wonder how likely this would be. > 4) cgit is modified to link against libgit2 Option 4) would be probably best in long term, but libgit2 doesn't exists yet. -- Jakub Narebski Poland ShadeHawk on #git -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
