From: maximilian attems <max@stro.at>
To: linux-kbuild@vger.kernel.org
Cc: sam@ravnborg.org, akpm@linux-foundation.org,
maximilian attems <max@stro.at>,
Andres Salomon <dilinger@debian.org>
Subject: [PATCH 1/7] deb-pkg: Beautify changelog
Date: Tue, 31 Mar 2009 17:19:26 +0200 [thread overview]
Message-ID: <1238512772-21180-1-git-send-email-max@stro.at> (raw)
Try harder to find email and maintainer name.
Debian's own devscripts all use DEBEMAIL or DEBFULLNAME
prior to an eventual EMAIL or NAME environment variable.
Match their logic.
"Anonymous Maintainer" sounds nicer then Kernel compiler
if no name is found. As bonus add more descriptive changelog
entry.
Cc: Andres Salomon <dilinger@debian.org>
Signed-off-by: maximilian attems <max@stro.at>
---
scripts/package/builddeb | 25 ++++++++++++++++++++-----
1 files changed, 20 insertions(+), 5 deletions(-)
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 1264b8e..dd61591 100644
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -66,14 +66,29 @@ EOF
chmod 755 "$tmpdir/DEBIAN/$script"
done
-name="Kernel Compiler <$(id -nu)@$(hostname -f)>"
+# Try to determine maintainer and email values
+if [ -n "${DEBEMAIL}" ]; then
+ email=${DEBEMAIL}
+elif [ -n "${EMAIL}" ]; then
+ email=${EMAIL}
+else
+ email=$(id -nu)@$(hostname -f)
+fi
+if [ -n "${DEBFULLNAME}" ]; then
+ name=${DEBFULLNAME}
+elif [ -n "${NAME}" ]; then
+ name=${NAME}
+else
+ name="Anonymous Maintainer"
+fi
+maintainer="${name} <${email}>"
# Generate a simple changelog template
cat <<EOF > debian/changelog
linux ($version-$revision) unstable; urgency=low
- * A standard release
+ * New upstream release
- -- $name $(date -R)
+ -- ${maintainer} $(date -R)
EOF
# Generate a control file
@@ -83,7 +98,7 @@ cat <<EOF > debian/control
Source: linux
Section: base
Priority: optional
-Maintainer: $name
+Maintainer: $maintainer
Standards-Version: 3.6.1
Package: $packagename
@@ -105,7 +120,7 @@ cat <<EOF > debian/control
Source: linux
Section: base
Priority: optional
-Maintainer: $name
+Maintainer: $maintainer
Standards-Version: 3.6.1
Package: $packagename
--
1.6.2.1
next reply other threads:[~2009-03-31 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 15:19 maximilian attems [this message]
2009-03-31 15:19 ` [PATCH 2/7] deb-pkg: Fix Provides field maximilian attems
2009-03-31 15:19 ` [PATCH 3/7] deb-pkg: bump standards version maximilian attems
2009-03-31 15:19 ` [PATCH 4/7] deb-pkg: Fix Section and Source field maximilian attems
2009-03-31 15:19 ` [PATCH 5/7] deb-pkg: Generate a debian/copyright maximilian attems
2009-03-31 15:19 ` [PATCH 6/7] deb-pkg: Fix generated packagename maximilian attems
2009-03-31 15:19 ` [PATCH 7/7] deb-pkg: generate changelog, copyright and control on demand maximilian attems
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1238512772-21180-1-git-send-email-max@stro.at \
--to=max@stro.at \
--cc=akpm@linux-foundation.org \
--cc=dilinger@debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.