[mythtv-commits] Ticket #7090: Updates for the rpm packaging scripts/spec
MythTV
mythtv at cvs.mythtv.org
Fri Sep 18 01:14:31 UTC 2009
#7090: Updates for the rpm packaging scripts/spec
----------------------------------------+-----------------------------------
Reporter: jtwyford at gmail.com | Owner: mdean
Type: enhancement | Status: new
Priority: minor | Milestone: unknown
Component: Contributed Scripts & Apps | Version: head
Severity: medium | Resolution:
Mlocked: 0 |
----------------------------------------+-----------------------------------
Comment(by jarod):
Replying to [comment:2 jtwyford at gmail.com]:
> Replying to [comment:1 jarod]:
> > Replying to [ticket:7090 jtwyford at gmail.com]:
> > > I've been working on updates to both build_myth.sh and mythtv.spec
for some time to keep up with trunk and generally streamline things.
> >
> > Um... I fail to understand what needed changing... I've been building
weekly svn trunk packages in RPM Fusion...
>
> Maybe I haven't been looking in the right place...
http://download1.rpmfusion.org/free/fedora/development/x86_64/os/ has svn
rev 21778 built just 4 days ago, and I've got newer stuff I'll build
tonight after testing some imon lcd icon patches...
> >
> > > Primarily: -themes is now built as part of mythtv.spec and is not a
package of all its own. Thus build_myth.sh has been streamlined too.
However, installing via the script still makes a rather boneheaded
assumption that is flat out wrong most of the time.
> >
> > Do Not Want. Very BAD for packaging. The themes should be a noarch
package of its own. After release, the themes typically don't need to be
updated, but the code does. Including the themes in the base package means
that we'd be pushing out a new themes bundle every time we pushed an svn
fixes update package, which is a huge waste of bandwidth. No thanks. :)
>
> It's still in its own noarch mythtv-themes subpackage, just getting
built via mythtv.spec, not via mythtv-themes.spec.
Being in its own noarch sub-package is irrelevant. Its still a sub-package
of the main package. Update the main package and you get an "updated"
themes sub-package. Gobs of rpm-newer package data that has to be pushed
around to mirrors, gets downloaded by users for no good reason, etc. All
but the base themes stay in a separate package.
> > > Also:[[BR]]
> > > * mythbackend now runs as the no-privilege user 'mythtv' that gets
added during install instead of root.[[BR]]
> >
> > Doesn't work cleanly. On startup, the backend starts before a user has
logged in. The only user with read/write privs on tuner devices is root.
Chowning devices in the initscript is not particularly cool either
(haven't looked to see if you're doing this yet).
>
> All I've done differently is add mythtv to the video group and the one-
liner to the init script.
Looks like that would work for analog v4l capture devices, but falls down
for dvb devices, making it no-go. Fedora probably ought to create its dvb
devices with the video group ownership too though, then this approach
probably would work.
> > > 3. Does the mythtv user/group still need to exist/be created?
> >
> > Probably not.
> >
> > > Why not some other already-defined non-privileged user?[[BR]]
> >
> > Such as? (And what for?)
> That was supposed to be if instead of why... Mainly, one less network-
facing process running as root.
Well, whatever user it is, for the scheme to work, if/when dvb devices
have video group ownership, the user would need to be a member of the
video group, which no users are by default, as far as I can see, so I
think we probably need to keep creating the mythtv user.
> > Will look 'em over in a bit. Kids need to be put to bed first...
> Thanks for the pointers. Updates to the spec when I get back from
dinner.
Still haven't got the last kid in bed, they're being particularly...
testing... tonight... So I haven't looked yet, but will in a few. :)
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/7090#comment:3>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list