X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/9d7f96cb8b87ed53bd93883b1519c7ad8a382819..ed1673929562adb8747b2e6dca424df92d210013:/doc/todo/parse_debian_packages.mdwn?ds=inline diff --git a/doc/todo/parse_debian_packages.mdwn b/doc/todo/parse_debian_packages.mdwn index af2547734..2425645d9 100644 --- a/doc/todo/parse_debian_packages.mdwn +++ b/doc/todo/parse_debian_packages.mdwn @@ -8,6 +8,8 @@ a helpful index page to a small repository, listing all the packages, and possibly their descriptions as well, with links to download them or their sources. +--Cameron + > It's a good idea, I think there are probably several ways to approach it > that would all yeild good, though differing results. Maybe with > something like this I'd actually get around to posting ikiwiki debs to @@ -31,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. @@ -55,6 +64,7 @@ automatically. >> a separate package from ikiwiki. Is it possible to package >> plugins separately? --Cameron ---Cameron +>>> Sure, a plugin is just a perl library so can easily be packaged +>>> separately. -[[tag wishlist]] +[[!tag wishlist]]