Summary: | TEST-REQUEST: Kimdaba 2.0 - needs amd64 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ian Monroe <gentoo> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | amd64 |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://ktown.kde.org/kimdaba/download-source.htm | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 67644 | ||
Bug Blocks: | |||
Attachments: |
Kimdaba 2.0, libkexif, libkipi and kipi-plugins
Kimdaba ebuild by itself |
Description
Ian Monroe
2004-10-18 10:22:32 UTC
Created attachment 42116 [details]
Kimdaba 2.0, libkexif, libkipi and kipi-plugins
The ebuilds for it all. They seem to work, but I don't have much ebuild
experience.
Created attachment 42117 [details] Kimdaba ebuild by itself Oh, ignore the libkexif, libkipi and kipi-plugins in the attachment. Bug #67644 already deals with those and appears to do a better job of it. committed, would some amd64 herd dev keyword again, please!? unless I'm not seeing something, the commited ebuild doesn't depend on libkexif (it is in gphoto's DEPEND). Ian, I'm not sure waht you want to say with this comment. KimDaBa doesn't reference libkexif, if I do not miss something. The kipi-plugins do, but these are not a dependecy of KimDaBa. ah, well I guess the fact that kipi-plugins depends on libkexif would be what I missed. I looked at libkipi and it doesn't have much docs to speak of. But if you grep its configure, there are plenty of references to kexif. And the kimdaba docs say to compile libkexif first. But that would be a seperate ticket I suppose. Ian: the references look like upstream uses one makefile for all the packages that's all. amd64 herd: Drop a line, if I'm pushing too much. :) ~amd64 again, looks good so far |