aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-09-16 15:28:12 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-09-16 15:28:12 +0000
commit2ab0fdeffc04515b97f4eb86efa2468fe69654e7 (patch)
tree257007fe41bee398d249bb831185856cd02ccaf5 /doc
parent50e5e6a5d4faaf43ac97020ee9fb1bd3bd6005c9 (diff)
downloadikiwiki-2ab0fdeffc04515b97f4eb86efa2468fe69654e7.tar
ikiwiki-2ab0fdeffc04515b97f4eb86efa2468fe69654e7.tar.gz
web commit by brlink: describe reprepro hooks
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/parse_debian_packages.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/parse_debian_packages.mdwn b/doc/todo/parse_debian_packages.mdwn
index 2e6ce3ef1..266686605 100644
--- a/doc/todo/parse_debian_packages.mdwn
+++ b/doc/todo/parse_debian_packages.mdwn
@@ -33,6 +33,13 @@ would then not be picked up until the ikiwiki is recompiled.
>> reprepro doesn't seem to have one, :( though of course creating a
>> script to do both would work (but it's not optimal). --Cameron
+>>> reprepro has two kind of hooks that could be used. One is called
+>>> whenever a Packages file is changed (normaly used to generate
+>>> Packages.diff files, but it does not need to add new files).
+>>> The other (though only available since 2.1) is called whenever
+>>> a package is added or removed (there is an example in the docs
+>>> for extracting changelogs using this).
+
> For ikiwiki to notice that the Packages file outside its tree has
> changed and things need to be updated, a `needsbuild` hook could be
> used. This seems very doable.