diff options
| author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-08-04 06:27:02 +0000 |
|---|---|---|
| committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-08-04 06:27:02 +0000 |
| commit | b55dfcd03d81257e4794f5f6762d27c013f8aa3d (patch) | |
| tree | 2eb976bc6c4d9fdee3a2a023f554f9034cfb61f6 /doc/todo/parse_debian_packages.mdwn | |
| parent | c38dd537e92ac6be58560aba292446787265a9e5 (diff) | |
| download | ikiwiki-b55dfcd03d81257e4794f5f6762d27c013f8aa3d.tar ikiwiki-b55dfcd03d81257e4794f5f6762d27c013f8aa3d.tar.gz | |
comments and updates a-la-airplane
Diffstat (limited to 'doc/todo/parse_debian_packages.mdwn')
| -rw-r--r-- | doc/todo/parse_debian_packages.mdwn | 21 |
1 files changed, 20 insertions, 1 deletions
diff --git a/doc/todo/parse_debian_packages.mdwn b/doc/todo/parse_debian_packages.mdwn index d1337665c..e34aa67e3 100644 --- a/doc/todo/parse_debian_packages.mdwn +++ b/doc/todo/parse_debian_packages.mdwn @@ -8,6 +8,11 @@ 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. +> 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 +> the repo. ;-) --[[Joey]] + I think this is easily possible (and I might be able to work on it myself, though Perl is not my strong suit). The trickiest part is probably figuring out how and when to parse the packages. @@ -18,6 +23,15 @@ reprepro/debarchiver/etc.). Or, the packages could be kept separate, with only a link given to the plugin, though changes 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.) +> +> 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. + Perhaps a better (though infinitely more complicated) solution would be to include the reprepro/debarchiver functionality in ikiwiki. Packages could be posted, like blog entries, and tagged @@ -25,7 +39,12 @@ with the target distribution (sid/lenny/etc.). Then compiling ikiwiki would generate the needed Packages/Release files automatically. +> I like the idea of +> using packages as "source" and spitting out apt repos, though I'd not +> 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 -[[tag wishlist]]
\ No newline at end of file +[[tag wishlist]] |