Thus said "John L. Poole" on Tue, 19 Nov 2013 05:12:08 -0800: > The reason I'm writing to this list is to inquire if there will be a > new release coming shortly or if I should try to create an ebuild > that incorporates the patch that fixes this problem?
I think it would be safest just to wait for the next release. Here are some issues you'll need to consider if you go the patch route: 1) Do you patch just this one bug fix? 2) If you patch the zip archive of the source the version identifier reported by your patched version and the non-patched will report the same. Making bug reporting difficult. 3) To avoid 2, you can merge/commit the patch into a private branch in a cloned copy of the fossil repository. Then extract the patch from there as a diff from the official released version and your branch. I don't know when the next official release will be, but this will give you an idea of the historical trend: http://www.fossil-scm.org/index.html/timeline?t=release Andy -- TAI64 timestamp: 40000000528c4bdd _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
