New wersion brasero is avaliable Reproducible: Always
*** Bug 254828 has been marked as a duplicate of this bug. ***
Created attachment 178765 [details, diff] configure.in differences between 2 releases Output of svn diff http://svn.gnome.org/svn/brasero/tags/BRASERO_0_8_4/configure.in http://svn.gnome.org/svn/brasero/tags/BRASERO_0_9_0/configure.in
Created attachment 178766 [details, diff] Diff against 0.8.4 ebuild
I added an diff against latest ebuild reflecting dependency changes between 2 releases Attachment #178765 [details, diff] and partially fixing bug #248275 (It should be decided if blockers between gnome-extra/nautilus-cd-burner and brasero is needed). Thanks
(In reply to comment #0) > New wersion brasero is avaliable > > Reproducible: Always > Now brasero 0.9.1 is avaliable
+*brasero-0.9.1 (23 Jan 2009) +*brasero-0.8.4-r1 (23 Jan 2009) + + 23 Jan 2009; Peter Alfredsen <loki_val@gentoo.org> metadata.xml, + brasero-0.8.2.ebuild, -brasero-0.8.3.ebuild, -brasero-0.8.4.ebuild, + +brasero-0.8.4-r1.ebuild, +brasero-0.9.1.ebuild: + Bump to 0.9.1, bug 254838. libgnome is no longer a dependency. W.r.t. bug + 248275, add nautilus useflag. Add cdrtools and cdrkit use flags, since + they are now selectable, do not make them default on. IUSE="+libburn", + libburn is now used whenever possible, which should be 90% of cases, + according to upstream. Backport these changes to brasero-0.8.4-r1 and punt + old versions. +
Only for information, Why is libburn prefered over cdrkit? Or should I ask this directly to upstream? Thanks :-)
(In reply to comment #7) > Only for information, Why is libburn prefered over cdrkit? Or should I ask this > directly to upstream? Thanks :-) http://mail.gnome.org/archives/brasero-list/2008-September/msg00001.html As to why, I don't know.
OK, thks =)