a a wrote:
> Mark Clarkstone wrote:
> > a a wrote:
> > > Mark Clarkstone wrote:
> > > > Basem Alsaeed wrote:
> > > > > Mark Clarkstone wrote:
> > > > > > I'm currently looking into providing an alternative repo for 4.2 on raspbian, at least until doozer has support.
> > > > > Thanks a lot Mark for your reply and for your effort :) much appreciated
> > > >
> > > > Sorry for not replying sooner guys, but in case you weren't aware I've setup a bintray repo that has builds for both tvh stable & unstable. Both builds are done in a chroot on a spare Pi2 of mine.
> > > >
> > > > I'm in the process of setting up another arm system to provide Debian jessie/stretch and Raspbian Stretch builds.
> > > >
> > > > Info is at the bottom of [[AptRepository]].
> > >
> > >
> > > I notice you're doing the builds manually. You could try setting up an executable shell script that's run with a daily cronjob as I detail above.
> >
> > That's the next thing on my list, I just wanted to make sure my scripts are working. :)
>
> Okay, no worries. Give me a shout if you need any info.
> After making the Update.sh file containing the above code located in /home/pi/CronJobs executable I made a text file named UpdateScript in /etc/cron.d containing the line:
>
> 0 6
* pi /home/pi/CronJobs/Update.sh
>
> Which makes the Update.sh script run every morning at 6am. So I wake up to the Pi nicely updated each morning.
Cool, I'm not actually running an RPi image, all my Pis are installed using "Raspbian (minimal) unattended netinstaller"
My build script also checks & only builds if there have been changes to the repo, so I just run
bash tvheadend-build-raspbian.sh master noforce mpmc
:p