resp

[ikiwiki.git] / doc / todo / parse_debian_packages.mdwn

diff --git a/doc/todo/parse_debian_packages.mdwn b/doc/todo/parse_debian_packages.mdwn
index e34aa67e36d2814acf89ecc825978d1f33e6bf90..2e6ce3ef12eb7c2c519ddae92ba3d95bdd8308ba 100644 (file)
--- 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
@@ -27,7 +29,10 @@ would then not be picked up until the ikiwiki is recompiled.
 > This could be done by adding a hook to reprepro/whatever that calls
 > ikiwiki --refresh at the end of updating a repo. (I don't
 > remember if reprepro has such hooks; mini-dinstall certianly does.)
-> 
+
+>> reprepro doesn't seem to have one, :( though of course creating a
+>> script to do both would work (but it's not optimal). --Cameron
+
 > 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.
@@ -44,7 +49,15 @@ automatically.
 > want to use it for a big repo, and I'd ideally want to keep the packages
 > in a different svn repo, pulled in via svn:externals.
 
-Just some thoughts I had, hope it's not too crazy.<br>
---Cameron
+>> I like it too, more than the easier options, why are the most
+>> interesting solutions always the most complicated? ;)
+
+>> Parsing the files sounds like it might require some outside
+>> dependencies, and given the complexity maybe this should be
+>> a separate package from ikiwiki. Is it possible to package
+>> plugins separately? --Cameron
+
+>>> Sure, a plugin is just a perl library so can easily be packaged
+>>> separately.
 
 [[tag wishlist]]