Import Debian changes 0.0~git20180821.e1733b1-1
git-fat (0.0~git20180821.e1733b1-1) unstable; urgency=low * Initial release.
This commit is contained in:
parent
eb2d41f476
commit
a77b316fa3
10 changed files with 447 additions and 0 deletions
21
debian/control
vendored
Normal file
21
debian/control
vendored
Normal file
|
@ -0,0 +1,21 @@
|
|||
Source: git-fat
|
||||
Section: vcs
|
||||
Priority: optional
|
||||
Maintainer: Marcel Kapfer <opensource@mmk2410.org>
|
||||
Build-Depends: debhelper (>=11~)
|
||||
Standards-Version: 4.1.4
|
||||
Homepage: https://github.com/jedbrown/git-fat
|
||||
|
||||
Package: git-fat
|
||||
Architecture: any
|
||||
Multi-Arch: foreign
|
||||
Depends: ${misc:Depends}, ${shlibs:Depends}, rsync, python2
|
||||
Description: Simple way to handle fat files without committing them to git
|
||||
Checking large binary files into a source repository (Git or otherwise) is a
|
||||
bad idea because repository size quickly becomes unreasonable. Even if the
|
||||
instantaneous working tree stays manageable, preserving repository integrity
|
||||
requires all binary files in the entire project history, which given the
|
||||
typically poor compression of binary diffs, implies that the repository size
|
||||
will become impractically large. Some people recommend checking binaries into
|
||||
different repositories or even not versioning them at all, but these are not
|
||||
satisfying solutions for most workflows.
|
Reference in a new issue