Internal SVN update option? (1 Viewer)

[nst6563]

Would it be possible to have an option in MediaPortal (via the Settings menu maybe?) to be able to choose to automatically update itself to the latest SVN build out there?

As in, select the option in the Settings menu (this option could be enabled/disabled also like all other menu items) and MP will recognize what version it is, then check for the latest SVN and if a newer SVN build exists than the one that's currently running MP will then d/l the newest svn to a temp folder, setup a batch job or scheduled task or kick off a new process (MPupdate.exe maybe), close down, make a backup of itself, unzip/rar the files into the MP folder, run start.bat, then re-start itself.

Another feature to go along with this would be the ability to restore the most recent backup in case the latest SVN didn't work out.

I'd find this feature particularly useful myself as I think some others would also after seeing posts regarding "how do I get the latest SVN?".

thoughts?

 

[ASiDiE]

People also need to understand that SVN files are NOT patches. They are the daily work of the Dev's. They are not to be installed on top of eachother.

 

[mPod]

They are not to be installed on top of eachother.

Sure they are. As long as you step up and not down.

 

[infinite.loop]

A SVN-Snapshot is:
x not a Bugfix
x not a official Patch
x not a official Upgrade

SVN-Snapshots are builds of the current stage of developement. Therefor no one should expect that they are stable.
Its very likely that with automatically applied SVN-Snapshot your MediaPortal installation will become unusable after a few days or after the first upgrade.

We use SVN-Snapshots to test new features and bugfixes between the relases versions of MediaPortal.

Always created a backup of your MediaPortal installation before you test an SVN-Snapshot.

 

[NLS]

erm sorry to move (just a bit) away from the core of the topic but...

erm... do SVN patches HAVE to be applied one on top of another?

in other words if I need to move to today SVN should I first apply all the previous?

in yet other words, just downloading the latest SVN might make you miss some change that was in a previous?

one more way to say it, does SVN have the full diff from 0.2RC4 or just from the previous SVN?

 

[ronilse]

erm sorry to move (just a bit) away from the core of the topic but...

erm... do SVN patches HAVE to be applied one on top of another?

in other words if I need to move to today SVN should I first apply all the previous?

in yet other words, just downloading the latest SVN might make you miss some change that was in a previous?

one more way to say it, does SVN have the full diff from 0.2RC4 or just from the previous SVN?

No, you don't have to apply any other than the latest

Regards
Roy

 

[Efros]

I think the concept of SVN is misunderstood by a lot of people, there is the incredible urge to have the latest fastest bestest software. The latest SVN is not necessarily any of these, I download the SVN and check to see if any of the changes affect any of the areas that I have niggles in, if they don't address any of these then I dump that SVN. If they do then I backup my current install and apply the SVN.

 

[nst6563]

looks like the point of my post was taken as an "upgrade path" or "simplified patching mechanism" rather than what I really meant it to be.

I know what an SVN is, I know what CVS is, etc. I've done software development before.

However, I prefer not to hook up a keyboard/mouse to my htpc all the time (isn't one of the points of an HTPC to have full functionality via the convenience of a small remote??) to test out if the latest SVN build addresses any issues I may be having. Having an "automated" option in one of the menus would solve this. My other option is to write the program myself when I have time. I simply figured that since MP is constantly under development, it would also benefit the dedicated testers in a way that's much faster and simpler to grab the newest build and begin testing.

 

[infinite.loop]

I've done software development before.

if this is the case you should know what that means.

a option to apply a SVN-Snapshot from inside MediaPortal is just stupid.

a option to apply a official bugfix or patch is a good idea, but a SVN-snaphot is not a bugfix or patch.
thats the reason why high has dissabled the SVN creation when this "tool" was relased.

 

[high]

I know what an SVN is, I know what CVS is, etc. I've done software development before.

so for you it should be a 5min job to write a batch grabbing the latest file and unpack it. +5 for a backup function and a task to grab nightly, thats it. Wheres the problem? Just keep it private please.

We (I) dont add this function inside MP for every user for good reasons. Its nonsense to believe you can always get the latest sources but need no mouse/keyboard to backup or change settings. That doesnt work, especially after 0.2 when new features will come up.
If this easy way is added it will be used. Even if you dont understand what you do or what SVN-versions are all about. Lets see the fun if a failed automatic snapshot ruined xxx installations.

btw. sometimes it can be helpfull to use the 'search'-function, this was already discussed in the past more then once.