|author||Sean Whitton <email@example.com>||2016-10-29 07:35:32 -0700|
|committer||Ian Jackson <firstname.lastname@example.org>||2016-10-30 17:27:52 +0000|
dgit-user(7): Explain "binary package"
Signed-off-by: Sean Whitton <email@example.com>
Diffstat (limited to 'dgit-user.7.pod')
1 files changed, 4 insertions, 3 deletions
diff --git a/dgit-user.7.pod b/dgit-user.7.pod
index d27cd93..ac983b4 100644
@@ -9,7 +9,7 @@ system
as if your distro used git to maintain all of it.
You can then edit it,
-build updated binary packages
+build updated binary packages (.debs)
and install and run them.
You can also share your work with others.
@@ -72,7 +72,8 @@ Later:
dgit clone needs to be told the source package name
-(which might be different to the binary package name)
+(which might be different to the binary package name,
+which was the name you passed to "apt-get install")
and the codename or alias of the Debian release
(this is called the "suite").
@@ -354,7 +355,7 @@ The C<dgit/jessie> branch (or whatever) is a normal git branch.
You can use C<git push> to publish it on any suitable git server.
Anyone who gets that git branch from you
-will be able to build binary packages
+will be able to build binary packages (.deb)
just as you did.
If you want to contribute your changes back to Debian,