On Sat, Aug 21, 2010 at 08:18:24PM -0400, Felipe Sateler wrote:
On 21/08/10 18:00, eighthave-gu...@users.alioth.debian.org wrote:
The following commit has been merged in the master branch:
commit b50fc79d8a856062d9a05100dd83a7fca3bf696b
Author: Hans-Christoph Steiner <h...@eds.org>
Date:   Sat Aug 21 17:43:50 2010 -0400

    added gitignore for clean git-status

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..3c2f99e
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,7 @@

I can't think of any reason not to do this... but we don't seem to have this in any of our other packages (or at least, most). Any reason why we haven't done this before?

I dislike silencing cruft, as in my packaging development routines cruft is a sign of something potentially forgotten or gone wrong:

A normal packaging build and successive cleanup should leave no traces behind[1].

 - Jonas

[1] Currently this is not always true when using patches and dpkg source format 3.0 (quit). That is a special case, however, which hopefully will be resolved upstream in dpkg-source and/or git-buildpackage. Until then I personally work around it locally - I noticed that others hardcode workarounds in packaging. which I dislike but (until now) have silently ignored.

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to