|
60 | 60 | <arg><option>--git-export=</option><replaceable>TREEISH</replaceable></arg> |
61 | 61 | <arg><option>--git-[no-]pristine-tar</option></arg> |
62 | 62 | <arg><option>--git-[no-]pristine-tar-commit</option></arg> |
| 63 | + <arg><option>--git-[no-]pristine-lfs</option></arg> |
| 64 | + <arg><option>--git-[no-]pristine-lfs-commit</option></arg> |
63 | 65 | <arg><option>--git-[no-]-purge</option></arg> |
64 | 66 | <arg><option>--git-tag-only</option></arg> |
65 | 67 | <arg><option>--git-retag</option></arg> |
|
105 | 107 | </listitem> |
106 | 108 | <listitem> |
107 | 109 | <para> |
108 | | - Build an orig tarball if it doesn't exist. Optionally using &pristine-tar;. |
| 110 | + Build an orig tarball if it doesn't exist. Optionally using &pristine-lfs; or &pristine-tar;. |
109 | 111 | </para> |
110 | 112 | </listitem> |
111 | 113 | <listitem> |
|
150 | 152 | <refsect2> |
151 | 153 | <title>Upstream tarball creation options</title> |
152 | 154 | <para>When &gbp-buildpackage; doesn't find a suitable upstream |
153 | | - tarball it will create one either using &pristine-tar; |
| 155 | + tarball, it will first try to check it out from &pristine-lfs;. If &pristine-lfs; |
| 156 | + doesn't produce a tarball, &gbp-buildpackage; will create one either using &pristine-tar; |
154 | 157 | or <command>git archive</command>. These options determine how the tarball is created: |
155 | 158 | </para> |
156 | 159 | <variablelist> |
|
164 | 167 | the <option>--git-upstream-tag</option>, <option>--git-upstream-tree</option> |
165 | 168 | options have no effect when creating tarballs. |
166 | 169 | </para> |
| 170 | + <para> |
| 171 | + If both <option>--git-pristine-tar</option> and <option>--git-pristine-lfs</option> |
| 172 | + are specified, <option>--git-pristine-lfs</option> takes precedence. |
| 173 | + </para> |
| 174 | + </listitem> |
| 175 | + </varlistentry> |
| 176 | + <varlistentry> |
| 177 | + <term><option>--git-pristine-lfs</option> |
| 178 | + </term> |
| 179 | + <listitem> |
| 180 | + <para> |
| 181 | + Use pristine-lfs when generating the upstream tarball if |
| 182 | + it doesn't exist. If this mode is enabled |
| 183 | + the <option>--git-upstream-tag</option>, <option>--git-upstream-tree</option> |
| 184 | + options have no effect when creating tarballs. |
| 185 | + </para> |
| 186 | + <para> |
| 187 | + If both <option>--git-pristine-tar</option> and <option>--git-pristine-lfs</option> |
| 188 | + are specified, <option>--git-pristine-lfs</option> takes precedence. |
| 189 | + </para> |
167 | 190 | </listitem> |
168 | 191 | </varlistentry> |
169 | 192 | <varlistentry> |
|
256 | 279 | tarball was generated and the pristine-tar data isn't already there. |
257 | 280 | </para> |
258 | 281 | </listitem> |
| 282 | + </varlistentry> |
| 283 | + <varlistentry> |
| 284 | + <term><option>--git-pristine-lfs-commit</option> |
| 285 | + </term> |
| 286 | + <listitem> |
| 287 | + <para> |
| 288 | + Commit the tarball to the pristine-lfs branch if a new |
| 289 | + tarball was generated and is hasn't been already imported there. |
| 290 | + </para> |
| 291 | + </listitem> |
259 | 292 | </varlistentry> |
260 | 293 | <varlistentry> |
261 | 294 | <term><option>--git-force-create</option> |
|
0 commit comments