[mythtv] mythtv branch master updated by gigem. v0.26-pre-1474-gf8cb433

David Engel david at istwok.net
Wed Nov 28 15:53:51 UTC 2012

On Wed, Nov 28, 2012 at 10:28:19AM -0500, George Nassas wrote:
> On 2012-11-28, at 8:23 AM, Karl Dietz wrote:
> > Both rules in your use case are of the same recording type (search). So
> > the functionality would not have had influence even if you used it.
> All recording rules are searches. The distinction in the example is
> one is more specific than another, channel vs any, and there has
> alway been an implicit hierarchy based on specificity. The most
> specific rule matches first, then the next and so on until the most
> general.

FYI, while rule precedence is baded on specificity, in the case of
search rules, the search criteria isn't considered.  A search is a
search is a search.  If you require a particular precedence in these
cases, you need to manually control it using the next precedence
criteria, which is recording rule ID.  That means you should create your
"more specific" rules first and your "less specific" rules later.

> The comment made it sound like that hierarchy was being removed
> which would be strange and puzzling. Looking at what was taken out
> it's just the ability to tweak the implicit hierarchy and that's no
> great loss.

Which is why it's been removed!

David Engel
david at istwok.net

More information about the mythtv-dev mailing list