<br><br><div class="gmail_quote">On Sun, Jun 7, 2009 at 6:04 AM, Michael Schwendt <span dir="ltr"><<a href="mailto:mschwendt@gmail.com">mschwendt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<a href="http://mschwendt.fedorapeople.org/audacious-2.0.1-0.1.fc10.src.rpm" target="_blank">http://mschwendt.fedorapeople.org/audacious-2.0.1-0.1.fc10.src.rpm</a><br>
<a href="http://mschwendt.fedorapeople.org/audacious-plugins-2.0.1-0.1.fc10.src.rpm" target="_blank">http://mschwendt.fedorapeople.org/audacious-plugins-2.0.1-0.1.fc10.src.rpm</a><br>
<br>
The included tarball is stripped for Fedora, to remove problematic<br>
files. Builds have been tested on F10 only. F11 is next.<br>
<br>
What will be needed is a maintainer for the -freeworld plugin packages.<br>
It shall be easy to modify above -plugins package and put back the<br>
original tarball, the required BR and configure options, and a<br>
desktop file for the MIME types.<br>
<br>
The API changes must be checked with every package that depends on<br>
audacious-devel.</blockquote><div><br>Nice work.<br><br>I would create a symbolic link audacious -> audacious2, so the previous<br>bin can still be called. <br><br>Something as <br><br>pushd %{buildroot}%{_bindir}<br>
ln -s %{name}2 %{name}<br>popd<br><br>before the clean section.<br><br>I would also call the libs package libs2, so the previous lib package do not need<br>to be removed during the upgrade.<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<div><div></div><div class="h5"><br>
> Meanwhile I'm almost done with preparing packages for Audacious 2.<br>
> Actually I have it running here already, but whereas I'm 99% done with<br>
> the -plugins package I still need to examine/rediff the patches in the<br>
> main package. It's not something I've done in one tiresome block as I've<br>
> almost started from scratch, only keeping fragments of the cleaned-up<br>
> 1.5.1 packages. Will publish them eventually prior to working on including<br>
> them in Fedora.<br>
><br>
> Some random observations:<br>
><br>
> There are API changes, which break external plugins, GVfs e.g. and header<br>
> locations. At least audacious-plugin-fc needs an updated implementation.<br>
><br>
> There are patches that still need to be applied upstream.<br>
><br>
> There is stuff in the packages which I consider questionable.<br>
> E.g. mp3/mpeg/wma related MIME types get removed from the main desktop<br>
> file, but also WAV and Ogg, then a hidden desktop file is added in the<br>
> -plugins package which readds the removed types although the needed<br>
> plugins are not available in the Fedora packages due to legal reasons.<br>
> The 3rd party packages could add such hidden desktop files. And actually<br>
> the main player is useless without the plugins package, so why add a<br>
> second hidden desktop file at all?<br>
><br>
> Audacious 1 and Audacious 2 cannot coexist, since only the executables<br>
> have different names. I don't think it is worthwhile to create symlinks<br>
> for the old executable names.<br>
<br>
--<br>
fedora-devel-list mailing list<br>
<a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-devel-list</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Paulo Roma Cavalcanti<br>LCG - UFRJ<br>