I was given this advice from Arthur, a Debian developer, but I can't find
some of the finer details I'm looking for:
-------
I recommend looking at
https://wiki.debian.org/UpstreamGuide to some
pointers about how to make it easy to ensure your software can be
easily packaged in Debian.
If you're looking to create a deb package that is ready to be included
in Debian it is best to have your debian/ directory on a separate
branch. I recommend using git-buildpackage, see
https://wiki.debian.org/PackagingWithGit (this is what most
collaboratively maintained packages use now).
For information on how to create Debian packages see
https://www.debian.org/doc/manuals/developers-reference/ (particularly
chapters 5 and 6). If you want to look at more of the background there
is the policy document, see
https://www.debian.org/doc/debian-policy/
There are a lot of tools for efficiently building Debian packages. If
you want to test your builds in a more controlled environment you
should probably use pbuilder (of cowbuilder) because those use a clean
chroot to build your packages to ensure you have the correct
dependencies specified.
Hope this helps
----------
Thanks
<div dir="auto"><div style="" dir="auto"><div style="width:352px;margin:16px 0px"><div style=""><div dir="auto" style="">I was given this advice from Arthur, a Debian developer, but I can't find some of the finer details I'm looking for:<div dir="
auto" style=""><br></div><div dir="auto" style="">-------</div><div dir="auto" style="">I recommend looking at <a href="
https://wiki.debian.org/UpstreamGuide" style="">
https://wiki.debian.org/UpstreamGuide</a> to some<br>pointers about how to make it
easy to ensure your software can be<br>easily packaged in Debian.<br><br>If you're looking to create a deb package that is ready to be included<br>in Debian it is best to have your debian/ directory on a separate<br>branch. I recommend using git-
buildpackage, see<br><a href="
https://wiki.debian.org/PackagingWithGit" style="">
https://wiki.debian.org/PackagingWithGit</a> (this is what most<br>collaboratively maintained packages use now).<br><br>For information on how to create Debian packages see<
<a href="https://www.debian.org/doc/manuals/developers-reference/" style="">https://www.debian.org/doc/manuals/developers-reference/</a> (particularly<br>chapters 5 and 6). If you want to look at more of the background there<br>is the policy document,
see <a href="
https://www.debian.org/doc/debian-policy/" style="">
https://www.debian.org/doc/debian-policy/</a><br><br>There are a lot of tools for efficiently building Debian packages. If<br>you want to test your builds in a more controlled
environment you<br>should probably use pbuilder (of cowbuilder) because those use a clean<br>chroot to build your packages to ensure you have the correct<br>dependencies specified.<br><br>Hope this helps<br></div><div dir="auto" style="">----------</div><
div dir="auto" style=""><br></div><div dir="auto" style="">Thanks</div></div></div></div><div style="height:0px"></div></div><div style="font-size:12.8px" dir="auto"><br></div></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)