Fwd: Re: Fwd: Re: [packman] Fwd: Packman Website, MythTV 0.20 RPMs für Suse 10.1

[Michael Schueller]

----------  Weitergeleitete Nachricht  ----------

Subject: Re: Fwd: Re: [packman] Fwd: Packman Website, MythTV 0.20 
RPMs für Suse 10.1
Date: Freitag, 15. September 2006 07:28
From: Thomas Börkel <thomas at boerkel.de>
To: Michael Schueller <schueller-berlin at gmx.de>, Simon Crute 
<simon at links2linux.de>

HI!

Thanks for forwarding to me, Michael.

Michael Schueller wrote:
>>> 1. mythtv-backend
>>> The service mythbackend should NOT be ON by default.
>
> I'm in two minds about this. In general, I agree, services should
>  be turned off by default. However in this case, I can't see why
>  mythbackend should ever been installed on a machine that isn't a
>  backend. And there's no security specific things that need to be
>  configured for the backend, so unless lots of people who think
> it shouldn't be, (or unless I'm breaking a packman rule I don't
> know of) I'll leave it as it is for now.

mythtv-setup needs mythtv-backend. And you need to be able to run
mythtv-setup on every machine. So, you end up with a enabled
 mythbackend service on a frontend only machine.

BTW: I do not need it, but isn't it Suse policy to have a
 rcmythbackend also?

>>> 2. libmyth
>>> libmyth is far too large. Something's wrong there with the
>
> For some reason the libraries aren't being stripped. I'll have an
>  upload tonight that should fix that.

Great! Thanks!

>>> 5. Updates to
>>>  http://cvs.mythtv.org/trac/log/branches/release-0-20-fixes
>>> Please update regularely the RPMs from 0.20 fixes branch and
>>> write the svn revision number into the packages description.
>>
>> This would really a good idea, but it would take time and this
>> release is the latest stable so far ...
>
> This is on my radar to do, but there's no way I can test at all
>  what I build. It will just be an automated script to do a
>  checkout, build and upload.

That's fine with me. BTW, you can save download time, if you only
 get a Subversion diff and use that as a patch in the .spec.

> And thanks for the feedback. (Even if it does mean more work for
> me ;-) ) Keep it comming.

Thanks!

Thomas

-------------------------------------------------------