[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Upstream tarballs with varying line endings



hello,

my problem is that Freeplane's git is configured such that native line
endings (LF on UNIX, CRLF on Windows) are used in checkouts and thus the
Upstream tarballs are either CR or CRLF, depending on on whose computer
the release(-tarball) was generated.

Now I see a few solutions:

1. fix this at upstream build time using an ant target
(by integrating http://ant.apache.org/manual/Tasks/fixcrlf.html)

2. write a get-orig-source target with code like this:

	find \( -iname \*.java -or \
	 -iname \*.xml -or \
	 -iname \*.mm -or \
	 -iname \*.MF -or \
	 -iname \*.properties \
	 \) -print0 \
	| xargs --null sed -i 's/\r$//'

(thanks to Harmut Goebel), generate freeplane-<version>+dfsg1.tar.gz and
import that.

3. Fix this at package build time like above, but I don't
think there is target that runs before the patches are applied
(http://www.debian.org/doc/manuals/maint-guide/dreq.en.html#targets)
          
Which one do you think is best?

Thanks and Best Regards,
-- 
Felix Natter


Reply to: