Re: [Freevo-devel] Binary releases

[Stefan v. d. E. <st...@ei...>]

Gustavo Sverzut Barbieri wrote:

> --- Stefan van der Eijk <st...@ei...> escreveu: 
>  
>
>>>>After exams, I should be able to finally finish my Debian package,
>>>>though I make no promises about it being 100% Debian standards
>>>>compliant since I'd have to split up a LOT of stuff to do that...
>>>>   
>>>>
>>>>        
>>>>
>>>That would be great. I make the source releases and the Gentoo
>>>      
>>>
>>ebuilds
>>    
>>
>>>(which is very simple, because the user compiles everything). Rob
>>>      
>>>
>>does
>>    
>>
>>>the "normal" binary release. We also have Redhat RPM and maybe
>>>Mandrake, too.
>>>
>>>      
>>>
>>I can help with the Mandrake packages.
>>
>>But I'm not very comfortable with the structure of the current rpm 
>>packages. To rebuild the src.rpm it BuildRequires the freevo-runtime 
>>package, which contain many things that are already in the Mandrake 
>>distribution. Why not use the software that a distro has already
>>made, 
>>and apply dependencies on the package to Require that software to be 
>>installed. This will also make builds on other platforms possible.
>>
>>    
>>
>
>
>There are few problems in using the distro default packages:
>1) They're commonly older than the ones we use
>
I take that challenge to get the mdk ones up2date.

>2) Sometime we need to apply our patches, like SDL_ttf
>
This patch:?
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/freevo/freevo/runtime/src/SDL_ttf2-patch2?rev=1.1&content-type=text/vnd.viewcvs-markup

Does this patch break anything, or can it safely be used by other 
programs too?

>3) Users may spend too much time downloading/finding every package
>
If you have a good dependency resolution system, then it's very easy. On 
mdk I can install squirrelmail on a bare system with one command. The 
installer takes care of all the dependencies --> the way it should be. 
Mdk uses urpmi --> http://www.urpmi.org/

>I was thinking like you sometime ago and mailed the list to discuss
>that... later I thought about it and now I'm convinced we should have
>those kind of packages... However I use the Freevo CVS and I got the
>libraries need myself.
>
>The good thing of that 3 package system is that the user needs nothing
>installed on the system, just that 3 packages. Other advantages is that
>since people/users are using a the same runtime libs, it's easier to
>developers to find the bugs.
>
The bad thing is that the runtime is only available for i586 --> binary 
release. While this covers the majority of the users this leaves out 
people running on other platforms. There seems to be a tendency towards 
multiple ports at the moment.

Also, the binary package may not always work, since it's not compiled 
within the same environment that it is running in.

I can understand why the runtime is shipped like it is, but I would 
appreciate if there would also be a way to build freevo to use the 
libraries provided on the system and not the freevo provided runtime.

regards,

Stefan