Hi Edward,

Debian has an amazingly complex toolchain. I am happy that
my own project (written in Perl) could be handled by the
Debian perl team. I did go through all those debian/ files
before. If you find a similar package to serve as a
model, you can get a lot from that.

Quilt, while cool, adds another layer. Since you are the
upstream author, you should be able to all patching
at that level, and avoid quilt entirely.

Cheers,

Joel

Edward Bartolo wrote:
> Hi,
>
> I am someone who is, unfortunately slow to learn new things, as my
> obstinacy was always on making logical sense out of what I learn.
>
> However, I am pleased to note that now, I can create rudimentary
> Debian packages. Next time, it will be some reading about the
> mysterious and bewitched debian/ subdirectory and what is the purpose
> of the most commonly used files.
>
> A simple and yet instructive reading would help place the foundations
> for a deeper understanding. I have to assimilate the basics first.
>
> Running dh_make creates a debian subdirectory filling it with numerous
> files. Most of these files are a mystery to me as I have still no idea
> what purpose they serve. However, running git commit on a local
> repository, and then running git-buildpackage does produce a .deb
> package, but without more knowledge, I am still too uninformed to do
> any useable maintainer's work even for packages that I myself created.
>
> Edward
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

--
Joel Roth