On Fri, 2021-10-29 at 15:28 +0200, Alec Leamas wrote:
> Other solutions could be creating a file like VERSION with relevant git
> data and add that to the distribution. That file can normally not be
> checked into git, it's a chicken and egg problem. The solution is to add
> the logic to
On 29/10/2021 07:35, Tobias Frost wrote:
On Thu, Oct 28, 2021 at 09:02:21PM -0500, Hunter Wittenborn wrote:
The problem is that whenever I (and the other guy) build the program with
something like debuild, the resulting .tar.xz archive doesn't contain the
.git repository in which the 'debian/'
On Thu, Oct 28, 2021 at 09:02:21PM -0500, Hunter Wittenborn wrote:
> Part of the packaging process for our program includes running Git
> commands to get things like the timestamp for when some files were last
> modified, which are used in things like the building of man pages via
> Asciidoc to
On Thu, Oct 28, 2021 at 09:02:21PM -0500, Hunter Wittenborn wrote:
> I, or mostly the work of another individual rather, is working on getting a
> program packaged for Debian for potential inclusion in the Debian
> repositories, but we've hit a roadblock in getting our package to work.
>
>
>
Hi,
On Thu, Oct 28, 2021 at 09:02:21PM -0500, Hunter Wittenborn wrote:
> Anything I could try?
I'm not sure this is a path very well travelled, but dpkg does in principle
seem to support a source package format called "3.0 (git)" where the source
tarball is basically a depth limited git-bundle.
I, or mostly the work of another individual rather, is working on getting a
program packaged for Debian for potential inclusion in the Debian repositories,
but we've hit a roadblock in getting our package to work.
Part of the packaging process for our program includes running Git commands to
6 matches
Mail list logo
