master
Joey Hess 2009-10-07 21:26:50 -04:00
parent 43a8b40032
commit f7601954a8
1 changed files with 12 additions and 4 deletions

View File

@ -238,10 +238,7 @@ sigh.
* `add_depends($page, $spec, links => 1, presence => 1)` * `add_depends($page, $spec, links => 1, presence => 1)`
adds a links + presence dependency. adds a links + presence dependency.
* `refresh` only rebuilds a page with a links dependency if * Use backlinks change code to detect changes to link dependencies too.
pages matched by the pagespec gain or lose links. (What the link
actually points to may change independent of this, due to changes
elsewhere, without it firing.)
* So, brokenlinks can fire whenever any links in any of the * So, brokenlinks can fire whenever any links in any of the
pages it's tracking change, or when pages are added or pages it's tracking change, or when pages are added or
removed. removed.
@ -413,3 +410,14 @@ Where to store the influence list? Well, it appears that we can just add
regular list of simple dependencies. So, the data stored ends up looking regular list of simple dependencies. So, the data stored ends up looking
just like what is stored today by the explicit dependency hacks. Except, just like what is stored today by the explicit dependency hacks. Except,
it's calculated more smartly, and is added automatically. it's calculated more smartly, and is added automatically.
> I've implemented influence calculation in `add_depends`. As expected,
> it means rather a lot more work, and makes some things much slower.
> Optimisation via `pagespec_match_depends` next.. --[[Joey]]
#### Influence types
Note that influences can also have types, same as dependency types.
For example, "backlink(foo)" has an influence of foo, of type links.
"created_before(foo)" also is influenced by foo, but it's a presence
type. Etc.