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 challenge we face on the final part of the project first task was to create a SPEC file. A SPEC file is to build on file that has a beta release list of instructions that will be used by a compilerbuilding tool to build our packages. Luckily for us The problems we faced with our build are a bunch or errors linking back to libraries that it cannot find and incorrect path names. After lots of Google searching and communication on Seneca’s Channel on IRC, we were able to reference fix that issue. The solutions to our work 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 an earlier version . To try to fix our issue we tried to email the package create of this compilerGCC, but sadly we did not hear back from them.

The first task was Since our attempt to create a spec SPEC file. A Spec was a disaster, we copied the SPEC file is file that has a list from the previous release of instructions that will be used by a building tool an older package and modified it to build fix our packagesneeds. The problem With the numerous amount of modification to the SPEC file we faced with started the build process, unlike our scratch SPEC file, the build is a bunch or times were significantly less. The errors linking back to libraries that it cannot findwould happen in the earlier stage of the build. After lots These errors consist of Google searching and communication on Seneca’s Channel on IRCmissing dependencies, missing files, we were able missing paths to directories. The missing dependencies are a easy fix that issue. After solving the issue we continued , I just needed to build install them, but this time the missing files, and other errors we came across an issue, that even Google cannot help us had trouble solving. Again with. To try to fix our issue we tried to email communication in the package create of GCCFedora community, but sadly we did not hear back from themwere unable to solve it. A suggestion was to do a command line build.

After speaking with the Fedora community, they suggested that we try to do a command line build from the GCC 4.5 tarball. With their advice, we extracted the GCC 4.5 file and started building from command line. The result of the compile the source and install it successfully into our system.