Closes: #382477
* section changing needs re-uploading orig.tar.gz.
Thanks, Adam D. Barratt. Closes: #387154
+ * binary files in diffs could be en/decoded with perl.
+ Thanks, Frank Küster. Closes: #397786
-- Andreas Barth <aba@not.so.argh.org> Sat, 11 Nov 2006 10:55:44 -0700
<!ENTITY % dynamicdata SYSTEM "dynamic.ent" > %dynamicdata;
<!-- CVS revision of this document -->
- <!ENTITY cvs-rev "$Revision: 1.307 $">
+ <!ENTITY cvs-rev "$Revision: 1.308 $">
<!-- if you are translating this document, please notate the CVS
revision of the original developer's reference in cvs-en-rev -->
The file should have a name that makes it clear which binary file it
encodes. Usually, some postfix indicating the encoding should be
appended to the original filename.
+Note that you don't need to depend on <package>sharutils</package> to get
+the <prgn>uudecode</prgn> program if you use <prgn>perl</prgn>'s
+<tt>pack</tt> function.
+The code could look like
+<example>
+uuencode-file:
+ perl -ne 'print(pack "u", $$_);' $(file) > $(file).uuencoded
+
+uudecode-file:
+ perl -ne 'print(unpack "u", $$_);' $(file).uuencoded > $(file)
+</example>
</footnote>.
The file would then be decoded and copied to its place during the
build process. Thus the change will be visible quite easy.