| Summary: | sci-biology/bioimagexd (new ebuild) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Avin Sigurani <embiopterid> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | CC: | mmokrejs, sci-biology |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://www.bioimagexd.net | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
VTK, ITK, and bioimageXD
modified cvs vtk modified cvs itk the bioimagexd ebuild |
||
|
Description
Avin Sigurani
2007-11-07 13:09:29 UTC
Created attachment 135420 [details] VTK, ITK, and bioimageXD I found an ebuild for ITK and modified it. VTK was already in the portage tree. The ebuilds have also been modified to compile in the specific way mentioned on http://wiki.bioimagexd.net/index.php?title=GettingStartedLinux . I know I have not done all of this correctly. I think bioimage specific options in ITK and VTK need to be optional. BioimageXD's various components should also be placed in the correct directories. There are also some other problems which I am not really able to diagnose that show up in the running bioimagexd program. I'm a bit of a newbie at constructing ebuilds, so feel free to give comments or suggestions. Comment on attachment 135420 [details] VTK, ITK, and bioimageXD Please, don't attach any tarballs. http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3#doc_chap2 Created attachment 135454 [details]
modified cvs vtk
Created attachment 135456 [details]
modified cvs itk
Created attachment 135457 [details]
the bioimagexd ebuild
(In reply to comment #2) Sorry about that. I had not yet read that document. No comments have been made on this bug report for some time. Is anyone still interested in integration of this package? If yes, please indicate that here in this bug report. Otherwise we'll resolve the bug in the near future, since we have an extremely large number of pending package requests and would like to focus... No response for six weeks. Resolving... |
