Publish.

[homepage.git] / blog / archive / 2016 / 02 / 02.rss

diff --git a/blog/archive/2016/02/02.rss b/blog/archive/2016/02/02.rss
index 1f41edb0124670feb692ea4e9008d20b66b81d40..be02699c9d13cd28c6fc38f04a1e32f1b471985f 100644 (file)
--- a/blog/archive/2016/02/02.rss
+++ b/blog/archive/2016/02/02.rss
@@ -11,7 +11,7 @@
                <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>        
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
                 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
-               <description>&lt;p&gt;Making packages for Debian require quite a lot of attention to
+               <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
 details.  And one of the details is the content of the
 debian/copyright file, which should list all relevant licenses used by
 the code in the package in question, preferably in
@@ -57,7 +57,7 @@ blog post from 2015&lt;/a&gt;.  To generate using cme, use the &#39;update
 dpkg-copyright&#39; option:
 
 &lt;p&gt;&lt;pre&gt;
-cme update dpkg-copyright -quiet
+cme update dpkg-copyright
 &lt;/pre&gt;&lt;/p&gt;
 
 &lt;p&gt;This will create or update debian/copyright.  The cme tool seem to
@@ -86,6 +86,23 @@ planet.debian.org.&lt;/p&gt;
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
+on how to use licensecheck and cdbs to create a draft copyright file
+
+&lt;p&gt;&lt;pre&gt;
+licensecheck --copyright -r `find * -type f` | \
+  /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
+&lt;/pre&gt;&lt;/p&gt;
+
+&lt;p&gt;He mentioned that he normally check the generated file into the
+version control system to make it easier to discover license and
+copyright changes in the upstream source.  I will try to do the same
+with my packages in the future.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
+against using -quiet for new users, so I removed it from the proposed
+command line.&lt;/p&gt;
 </description>
        </item>