Exclude .git directory from release tarballs
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
People
(Reporter: bugzilla, Unassigned)
Details
Steps to reproduce:
The release tarballs currently include the .git folder.
In the 5.0.4.1 release, this totals 78.8 MB, as contrasted with 9.8 MB for the rest of the files in the distribution.
Most of this is a single .pack file of about 75 MB (/.git/objects/pack/pack-f78f29791d82ee0955284b8e18e963d8e3dca6da.pack).
Is there any reason why the .git folder needs to be distributed with the rest of the code? Should it simply be ignored?
|
||
Comment 1•2 months ago
|
||
The idea was that people who have downloaded the tarball could easily update using git once they had it.
I'm betting we can probably do a thin clone of some sort that doesn't have the entire repo in it though. I'm pretty sure I've seen something where you can have it pull just the data for what you're actually checking out and enough info to find the repo to get the rest later...
|
Reporter | |
Comment 2•2 months ago
|
||
I see. Are there many people for who that is a valid use-case (as opposed to just cloning the repo directly)? Maybe there are, but it seems like unusual.
However, I might also the counter-point whereby a lot of people (myself included) prefer to manage their deployment solely via the release tarballs and in this situation that can lead to the risk that someone unwittingly does a git pull and messes up a live deployment. Also, if you are using version control to manage deployments then you either need to have an extra step to remove this folder when you do a new vendor drop or risk confusion or breakage by including the folder inside your deployment repo.
However, if there is a reluctance to remove the folder altogether then, yes, something like you suggest might be a possibility. Either way, it is clearly not sensible to keep it in the release at its current size!
Description
•