The release process contains a feature freeze phase during which development is focused on code review and bug squashing. The main resource for measuring code stability are our nightly builds and automated test cases on the various platforms. Exhaustive, manual testing is only performed on our core platforms Windows and Linux. You can identify a minor release on its version number -- only the last digit changes. Major Releases Major releases are more extensively tested and validated.
|Published (Last):||8 April 2008|
|PDF File Size:||16.48 Mb|
|ePub File Size:||12.85 Mb|
|Price:||Free* [*Free Regsitration Required]|
Add an attachment proposed patch, testcase, etc. Also, if you have a suggestion for a more appropriate "Group" field, let me know. It includes software for examining, constructing and converting DICOM image files, handling offline media, sending and receiving images over a network connection, as well as demonstrative image storage and worklist servers.
It comes in complete source code and is made available as "open source" software. Having dcmtk in Fedora is of great interest as it means that we can use it as both a server to receive and store DICOM medical images, and as a client to process them. Many software in the medical field make use of the dicom standard. You only need to install this if you are developing programs that use the dcmtk libraries.
Please compile with --with-private-tags so that the private tag file is included, it makes life with dcmdump much easier. Also, dcmtk Sorry for the extremely slow response.
I took most of your suggestions and added them to the SPEC file. A couple things. Any particular reason to do this? Regarding getting proper sonames for the libraries It it valid to just use some shell scripting to rename the current library. Also, should the libraries be stripped I took a quick look at the differences between dcmtk Any comments? And yeah, 3. Good to see this ball rolling again : pdcmtk contains only one add-on the new storescp placeholder fields added in r18 and r24 , and only one piece of changed behaviour r Concerning r45, this adds a patch that fixes problem with meta header information not being read correctly when the meta header is malformed incorrect size.
You can easily and safely back out these three changes, and use the remainder, which are only isolated bug fixes. I recommend reading the full commit history - it is not long. If you want, I can roll a patch for you against plain dcmtk As regards the development "3. Comment 7 Andreas Loening UTC Hi Per, I ended up incorporating almost everything with the following exceptions: 1 did not include the change to tlslayer.
The only remaining issue I think Do you know if this is a real blocker? Hello Andreas! Andreas, are you still interested in packaging this or will you hand over it to Mario?
Mario, did you ever get the soname issue worked out? Any ideas? Is having sonames a strict requirement for package inclusion? One of them was the use of Cmake! I believe a snapshot of that is what you are seeing at commontk. At this point since this has taken so long already , it might be just as well to wait for that release. These releases only occur every couple years. Also I removed charls and fixed almost all relevant errors. However there still is an error in how other libs links to dcmdata.
This seems not be related to charls removal as happens also when all the relevant patches are disabled. In the latter case - yes, you should consider providing your own ldconfig file. Take a look on how Qt resolves this issue. Otherwise your package looks good.
Btw do you plan to update to 3. As far as I know ver 3. What to do you think? I tried building the src rpm on Fedora 13, and that worked, but on install I got this: bash This is an issue and must be fixed. Great work. You should just remove them later dcmtk. See koji link above.
Note You need to log in before you can comment on or make changes to this bug.