harley at thepetersclan
Dec 23, 2010, 9:44 AM
On Wed, 22 Dec 2010 23:00:51 -0500
Re: Theme downloader site updated for trunk/master.
[In reply to]
Chris Pinkham <cpinkham [at] bc2va> wrote:
> * On Wed Dec 22, 2010 at 01:17:05PM -0600, Harley Peters wrote:
> > You can pull the TintedGlass theme via git if you want to from now
> > on.
> > git clone git://vps64.biterror.net/TintedGlass
> I received an error trying to clone this.
> "fatal: The remote end hung up unexpectedly"
Ok I moved the repo to a different location so I could run gitweb and
have it's log file layout match all my other web sites and for got to
update the git config file and restart it. :(
Should work now.
> > It contains both a master and 0.24 branch. There both identical
> > right now.
> > Also since your going by the themeinfo.xml major/minor numbers to
> > indicate an update to users can the minor number be multiple
> > digits ? Major/minor example: 1/18 (my theme is currently at
> > version 1.18)
> The major and minors are stored as ints, so multiple digits are fine.
> > Also do you have to update these themes manually ? I don't won't to
> > update the major/minor numbers to often if you do.
> Right now I'm updating them manually, but do want to setup a cron
> or something similar. Right now it's a 3-step process until we get
> our webserver rebuilt. Currently, I run my script to build/update the
> theme repository itself. Then I rsync it to my home directory on
> the webserver, then I ssh into the webserver and install it since
> I'm not rsyncing as root. Eventually my script can just run via
> cron on the webserver itself.
> You don't have to update the version number for every change you
> make. You could also have a branch that I pull from for MythTV
> master, but it doesn't have to be your master. So you can develop
> in your master then just merge over changes to the other branch when
> you bump the version number. For each theme for each version of
> MythTV, I store the repository and branch name to pull from, so for
> instance, I could pull for MythTV 0.24 from your 0.24 branch and
> for MythTV 'master' from your 'mythtv-master' branch.
> mythtv-theming mailing list
> mythtv-theming [at] mythtv
Ok I used your suggestion and created a mythtv-master branch which you
should pull from rather than master.
mythtv-theming mailing list
mythtv-theming [at] mythtv