Red Hat Bugzilla – Bug 864651
Include contrib/subtree for git-subtree command
Last modified: 2013-04-30 19:52:40 EDT
Description of problem:
The popular 'git subtree' command (https://github.com/apenwarr/git-subtree), commonly used as an alternative to 'git submodule' has been merged into contrib/subtree of the mainline git repository and is available as of git-1.7.11, with maintenance no longer continuing on the original project.
It would be great if Fedora's git was built with contrib/subtree, so users of 'git subtree' don't have to build git from source.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. git clone https://github.com/gitster/git.git
2. cd git
3. git subtree add -P ourSubtree https://github.com/gitster/git.git
git: 'subtree' is not a git command. See 'git --help'.
Subtree containing https://github.com/gitster/git.git repository should be created in 'ourSubtree' subdirectory (prefix)
git clone https://github.com/git/git.git
sudo make prefix=/usr
sudo make prefix=/usr install
sudo make prefix=/usr install-doc
Then command git subtree should be available.
Nice, thanks Tetra. This might be a good candidate for a new subpackage? That way we're not installing it by default and making folks think that it's an officially supported part of git.
(In reply to comment #2)
> Nice, thanks Tetra. This might be a good candidate for a new subpackage?
> That way we're not installing it by default and making folks think that it's
> an officially supported part of git.
I think we can just install it as other officially supported git-* stuff, i.e. into /usr/libexec/git-core/, can't we? What's benefit of the separate package?
If something happens to git-subtree and we remove it from the git package, it will be same impact for it's users as with git-subtree package. And the rest of users who doesn't use git-subtree at all won't notice anything.
It's certainly a valid concern as to what would happen if/when subtree becomes an official part of git. From packaging, I would think that we'd just add a provides/obsoletes to git at that time.
My main concern was causing confusion as to whether it was officially supported. If someone installs git from our packages and then takes bug reports or complaints to the git list, will our packaging it as part of git cause trouble for upstream or us? I may well be worried about nothing. :)
(We do include the completion script, which is currently in contrib, so there's one counter example.)
(In reply to comment #4)
> It's certainly a valid concern as to what would happen if/when subtree
> becomes an official part of git. From packaging, I would think that we'd
> just add a provides/obsoletes to git at that time.
> My main concern was causing confusion as to whether it was officially
> supported. If someone installs git from our packages and then takes bug
> reports or complaints to the git list, will our packaging it as part of git
> cause trouble for upstream or us? I may well be worried about nothing. :)
Since git-subtree is in the upstream git repository (although in contrib/), I think it is officially supported. We can forward bugs against it to upstream and we can also send them patches. So in my opinion we can safely include it in the main git pkg.
git-18.104.22.168-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing git-22.214.171.124-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
git-126.96.36.199-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.