Changes

Our Primary Goal and Focus was to package the DXR 'viewsource' web application tool and dependencies, (Dehydra and Jshydra), as a first step towards packaging the full DXR system for wide, reliable distribution. DXR contains components such as Dehydra, Jshydra, Viewsource, and a Modified GCC compiler. DXR was originally created by David Humphrey as an experiment. This experiment was designed to use static analysis data from mozilla's static analysis tools (Dehydra and Jshydra) in terms of source code cross-reference. We had to essentially build each of these packages from scratch in an attempt to put it all together and hopefully have it placed in the next Fedora 13/14 distribution.

Packaging is defined as the process of archiving files together along with information about the package, like its current version, a description of what the package is meant to do, etc. Packages are deployed in order to solve a software issue or resolve a package dependency. New version of packages are constantly coming out with new features, patches, and fixes that improve upon the last. Packages are what make up any Linux system and as such are a very fundamental part of any open source project. However, packaging is not limited to only open source projects, mainframe software, Windows software, etc. are all packaged.

The first task was to create a spec SPEC file. A Spec SPEC file is file that has a list of instructions that will be used by a building tool to build our packages. The problem problems we faced with our build is are a bunch or errors linking back to libraries that it cannot findand incorrect path names. After lots of Google searching and communication on Seneca’s Channel on IRC, we were able to fix that issue. The solutions to our problems are using the correct options to build and use patches that will alter the code. After solving the issue we continued to build but this time we came across an issue, that even Google cannot help us with. To try to fix our issue we tried to email the package create of GCC, but sadly we did not hear back from them.

After speaking with the Fedora communitySince our attempt to create a SPEC file was a disaster, they suggested that we try copied the SPEC file from the previous release of an older package and modified it to fix our needs. With the numerous amount of modification to do a command line the SPEC file we started the build process, unlike our scratch SPEC file, the build from times were significantly less. The errors would happen in the earlier stage of the GCC 4build.5 tarballThese errors consist of missing dependencies, missing files, missing paths to directories. With their adviceThe missing dependencies are a easy fix, I just needed to install them, but the missing files, and other errors we extracted had trouble solving. Again with communication in the GCC 4Fedora community, we were unable to solve it.5 file and started building from A suggestion was to do a command linebuild.