|
SageTV Studio Discussion related to the SageTV Studio application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the Studio software application should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
How to specify a minimum STV file set in a plugin manaifest?
How do I specify a dependency on a minimum STV file set? I'm updating plugins to take advantage of this change added by Opus4: http://forums.sagetv.com/forums/showthread.php?t=51602
It requires the STV file set to be at least 2010120101. Thanks, Tom
__________________
Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders. |
#2
|
||||
|
||||
Does anybody know the answer to this?
__________________
Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders. |
#3
|
|||
|
|||
There is a property in my extender properties that specifies that. Here is what mine shows:
version/STV_file_set=2011110601 |
#4
|
||||
|
||||
I would think that you should be able to do it with
Code:
<Dependency> <STV>SageTV7</STV> <MinVersion>7.0.23.0</MinVersion> </Dependency> |
#5
|
||||
|
||||
Quote:
@JREkiwi - That works for the core, but I want to specify a minimum STV fileset.
__________________
Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders. |
#6
|
||||
|
||||
What he showed you is an STV dependency, not a core dependency. His example requires a specific version of the STV file named SageTV7.xml. This is the right way to do what you want since you don't really care how the file got there; you just want to make sure it has the right contents.
__________________
-- Greg |
#7
|
||||
|
||||
Quote:
Code:
<Dependency> <Core></Core> <MinVersion>7.1.5</MinVersion> </Dependency> |
#8
|
||||
|
||||
I guess I'm not explaining myself well enough. I need to make sure the latest STV fileset is installed, which is 2011110601. (This is the update Andy put out to use the new weather sources.) I know the SageTV version is 7.1.9.256 but that can have different STV filesets. (I think the one before 2011110601 was 2011042501.)
__________________
Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders. |
#9
|
||||
|
||||
The STV file has its own version number (visible on the System Info screen) that may be different from the product core version number. The STV version is the one checked by the STV dependency. If you need a particular version of the STV (i.e. the UI, not the product core), you should use an STV dependency.
Or are you saying there's some other file in that particular update fileset that you depend on besides the STV file? If so, what is it? Maybe there's a way to check for that directly. Again, it's best to check for the specific files you need rather than depending on them having been delivered by a particular update.
__________________
-- Greg |
#10
|
||||
|
||||
Are you saying I'd do it like this:
Code:
<Dependency> <STV>SageTV7</STV> <MinVersion>2011110601</MinVersion> </Dependency>
__________________
Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders. |
#11
|
||||
|
||||
No, you should look up the STV version number in System Info (or open the STV in Studio and look at the version info under the Global theme) and use that number in your dependency. The update fileset number isn't interesting, because the dependency checker doesn't check that, and it might not be the only way to get that version of the STV. (Say for instance that Jeff releases a new installer that includes those changes without requiring any updates.)
This is all assuming that the STV is what you care about, and not some other random file in that update fileset.
__________________
-- Greg |
#12
|
||||
|
||||
Quote:
Code:
Current STV File: SageTV7.xml (Version 7.1.9.6, November 11, 2011, Name: SageTV7)
__________________
Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders. |
#13
|
||||
|
||||
For reference, the STV name and version that are used for this check are stored in the STV, at Global -> STVName, and Global -> STVVersion
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
MediaPlayer Plugin/STV Import: Winamp Media Player Plugin | deria | SageTV Customizations | 447 | 12-11-2010 07:38 PM |
feature / plugin request: Test if set top box is on | korben_dallas | SageTV Customizations | 0 | 03-15-2007 02:15 PM |
where to set .stv in placeshifter?? | JUC | SageTV Placeshifter | 6 | 12-12-2006 06:14 AM |
Minimum STV that supports commercial skipping? | jbromwich | SageTV Customizations | 1 | 05-17-2005 04:26 AM |