[mythtv] Packaging prereleases/CVS? (was: Next release?)

[Tim Harvey]

Chris,

I'm very interested in easily being able to create a package out of the
current CVS.  I've downloaded the spec files from your site but I can't
say that I know exactly how to use them.  Is there a simple process to
follow that you could outline?  Doesn't the inclusion of new files and
removal of old files break things?  I really don't like the idea of
installing my 'in development' version without a package as it seems to
put files all over the place making it difficult to move from version to
version.

Also, with regards to MythWeb, do you know of a simple way to get a
browser to 'launch' a file?  I have patched MythWeb to allow file
launching from links for MythMusic, MythVideo, and MythTV but I don't
like my solution.  I've tried using 'file://<network attached storage>'
but it always causes my browser (IE) to try to download the file instead
of just launching it.  My solution was to come up with a new protocol
such as 'media://' and then configure IE to launch my media player
application for that protocol.  I consider that quite a hack, especially
considering I have to make registry hacks to register the protocol.

Thanks for any help!

Tim

> -----Original Message-----
> From: mythtv-dev-bounces at mythtv.org
[mailto:mythtv-dev-bounces at mythtv.org]
> On Behalf Of Chris Petersen
> Sent: Friday, January 23, 2004 11:42 AM
> To: Development of mythtv
> Subject: Re: [mythtv] Packaging prereleases/CVS? (was: Next release?)
> 
> Sorry for not responding about this earlier, I've been overloaded with
> "life" lately and haven't had much time to think about myth stuff.
> Anyway...
> 
> > would it make sense to rethink about publishing packages of
> > prereleased versions, CVS or otherwise?
> > ...
> > Many projects have unstable/bleeding edge/beta packaged stages for
the
> > adventurous to lay their hand upon. What do you think?
> 
> I'm personally in favor of this.  Granted, I currently build my own
> packages from CVS (or will once this ../../.. qmake "feature" is
> resolved or worked around), but it would be nice to have official
> packages so I don't have to do this.
> 
> In my case, I refuse to install unpackaged software on my systems
unless
> there is a REALLY good reason - packages are just too nice to deal
> with.  As a developer on this project, I do occasionally need to keep
up
> with CVS.
> 
> Although I agree that it wouldn't be such a great idea having a link
to
> the CVS rpm's prominently featured with the other download links, I
> don't think such a link should be discouraged outright.  There are
> plenty of people capable of providing good bug reports, who wouldn't
> otherwise install CVS for debugging.  If there was an unofficial
> repository of cvs rpm's (not linked to from the myth web page, but
> somewhere we could publicly post/talk about, rather than Axel's
private
> one), those people could still use CVS.
> 
> If it becomes a major hassle, we could always go back to the way
things
> are now.
> 
> just my $.02
> 
> --
> Chris Petersen
> Programmer / Web Designer
> Silicon Mechanics:  http://www.siliconmechanics.com/
> Blade Servers:
http://www.siliconmechanics.com/c292/blade-server.php
> 1U Servers:         http://www.siliconmechanics.com/c272/1u-server.php
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev