<div>On 7/31/06, <a href="mailto:scdbackup@gmx.net">scdbackup@gmx.net</a> <<a href="mailto:scdbackup@gmx.net">scdbackup@gmx.net</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi, > the project has been revived and now lies at <a href="http://libburn.pykix.org">libburn.pykix.org</a> > Please post bugs, ask for enchantments/features, etc. :) Well, libburn could need some increased agility, that much is true. > As far as I could understand, the commits stopped two year ago, > and nothing was happening on the libburn front since then. There have been changes and enhancements in the beginning of this year (2006). My own project cdrskin currently uses a privately forked libburn-0.1.2 or a libburn-0.1.3 from CVS of february 2006 (with still one private enhancement, sigh). So it is not dead ... only very slow. Hopefully some of the maintainers will notice your announcement and a fruitful discussion can emerge.</blockquote><div> I would hope the same... </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > I really don't see this as a forking :) > We will continue with current codebase, and continue the things that > were started, nothing else :) It will be a fork as soon as the traditional maintainers make a change on their own version. So in order to be not a fork, it would need coordination. Being an involuntary libburn forker myself, i can hardly speak against a fork in general. Nevertheless, i do express my support for having a unified and stable API and for rejoining the forks into a common version from time to time. I myself do not strive for participating in the inner development of libburn but am mainly interested in getting the needs of cdrskin into a stable version of libburn. (There are two pending: my whitelist patch and my wish to burn on-the-fly with data read from stdin and no need to announce the track size in advance.) What are your plans about the next enhancement steps ? Would it be possible to expose a tarball with a snapshot of the current state of <a href="http://libburn.pykix.org">libburn.pykix.org</a> ? Have a nice day :) Thomas _______________________________________________ libburn mailing list <a href="mailto:libburn@lists.freedesktop.org">libburn@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/libburn">http://lists.freedesktop.org/mailman/listinfo/libburn </a> </blockquote></div>