Need help packaging MMS (My Media System) and get it into ubuntu

[Roman Müllenschläder]

Am Montag, 15. Januar 2007 12:37 schrieben Sie:
> Sorry for the late reply. I'm studying for my exams, so my presence is
> quite sporadic.
>
> On Fri, Jan 12, 2007 at 03:16:33PM +0100, Roman Müllenschläder wrote:
> > > > We just need to create some separate packages ... I could imagine
> > > > building 'mms-common' and some 'mms-desired-output' as MMS is able
> > > > to deal with various outputs (f.i. SDL, DXR3, FF-DVB).
> > >
> > > Sounds sensible.
> >
> > Mybe you would like to mail me personal, so we could see what packaged
> > should be created !?
>
> I'm still a bit confused. You say you've already created packages for
> Ubuntu/Debian, so what *exactly* is it you need help with?

I firstly need help getting the package into Debian/buntu ...

Therefore we firstly need to decide what packages should be created.
mms-sdl, mms-dxr3, mms-settop, mms-common ... whatever!?
I'm hardly able to decide nor to realy do it cause of not beeing firm in 
creating packages and esp. rules.

>
> > > > And why do we need a separate user? It won't run as daemon so it
> > > > should be fine running without creating a user ... !?
> > >
> > > The install target creates directories in /var/lib and /var/cache
> > > and I don't see it as an option to allow all users full access to
> > > those directories, so the obvious choice to me seemed to be to run
> > > it as a new, separate user.  The separate user will be made the
> > > owner of the relevant directories under /var and his .Xsession would
> > > be set to start mms on login. That way, all that would have to be
> > > done in order to use mms in a set top box setup, would be to let the
> > > display manager automatically log in the mms user.
> >
> > Yeah, this could be _one_ possibility ... but what if one wants to use
> > it as a 'normal' application?
>
> I wouldn't know. The config files are in /etc/ and we're not going to
> give full access to all users to them, so if a regular user wants to run
> it for himself, he'd probably create his own config files and storage
> hierarchy and such for it.

MMS has the possibility to do a 'make install-user' which installs everything 
into ~/.mms ... this will be a separate package then?

>
> > And what about users wanting to use a DXR3 or FF-DVB within a
> > settop-box-setup?
>
> Er... Yes, what about them?

see above for various packages

>
> > > > It by far seems to be a problem on this list to deal with
> > > > transparency,  particiption and cooperation ... or is that just my
> > > > feeling?
> > >
> > > The process for getting a new package into Ubuntu is described on
> > > https://wiki.ubuntu.com/MOTU/Packages/New .  A lot of effort has
> > > been put into making things transparent.  If you have anything
> > > concrete that you feel is not transparent enough, feel free to point
> > > it out and we'll do our best to fix it.
> >
> > It's not the process on packaging ...  I've done some work to get the
> > package done as you find it on www.prodeia.de/mms and we (the in MMS
> > involved users) are quite busy to fit all what is needed ...  As I
> > asked for help here, no one ever asked _how_ ... but the wheel is
> > always invented new ... that's what could be avoided with
> > transparency,  particiption and cooperation.
>
> I don't think I understand. What exactly is it that you feel is not
> transparent enough?

I thought firstly the upstream developers are the experts for their 
software ... so I thought the first steps are getting clear what software 
specific needs have to be translated into the deb. Not vice-versa ...

Lg
Roman

P.S. Can we keep this on the list? Would make it easier for me to keep 
track :)