Currently, I'm editing files directly with GitLab web interface. For the moment, I only want "packaging from git": Git -> Packaging helper (single direction sense)
Thanks. __________ I'm using this express-made address because personal addresses aren't masked enough at lists.debian.org archives. El 20/12/16 a les 15:25, Adam Borowski ha escrit: > On Tue, Dec 20, 2016 at 11:00:20AM +0100, Narcis Garcia wrote: >> Hello, I'm trying to maintain a small project in my public Git, and to >> have an easy way to build a package for Debian OS obtaining a good/clean >> result. >> After this, I will try to deploy my APT repository or contact some >> sponsor for Debian official repository. >> >> I'm executing this but I don't identify the problem: >> $ git-buildpackage >> Can the Git content be bad? Lack of files? Unnecessary files? Bad structure? > > Note that "packaging with git" is very distinct from "packaging with > git-buildpackage". The latter, despite the name, is merely one of many > possible workflows, and a very idiosyncratic one. It also suffers from > treating quilt as a god rather than an abomination it is. Using version > control checked into another version control is a disaster. > > Even just using git directly without any helpers is, IMO, much better -- you > can conveniently transfer patches both ways between your and upstream > repository, at every point you get an appropriate form for modification -- > you can just hack on the code (with something quilt-based you need to > finalize patches after every incremental edit), etc. > > Another option, much liked by everyone I hear, is dgit -- I only looked at > its very first iteration, though, with no tuits to check out a modern > version yet so I can't give meaningful advice, but a git-using workflow > that's not based on quilt can't possibly be worse than gbp :) > > > Meow! >
