JShydra Packaging cont.. Stage 1 complete.

This blog is a direct continuation to my last blog post "Packaging JShydra - Stage 1".

I left off with a problem within the %setup section of my spec file. The issue was that the %setup -n option had to be used for this macro. Instead of %setup -q I changed it to %setup -n jshydra.

For more info on the %setup macro, click here.

With that fixed, the next issue was: http://pastebin.org/100301

This problem was due to the fact that there is no makefile and therefore for I had to specify where the build should happen.

I edited the %install section to look like this: %install rm -rf %{buildroot} install -d %{buildroot}/var/www/html/jshydra

I ran the rpmbuild again and well, success! After running rpmlint, everything seems to be going alright.

Here are the results of rpmlint:



Click here for my SPEC file!

Next up... MOCK!

Packaging JShydra - Stage 1

It's been a while since I've blogged, feels kind of nice to get back on here actually. Continuing with the DXR project I have obtained a "packaging" role. My new job now aside from being the REPO master is to package JShydra.

JSHydra Description: JSHydra is a static analysis tool that is capable of performing analysis of general JavaScript code. It is inspired by the Dehydra and Treehydra tools, which can perform similar tasks in C++ code. In its back-end, it uses the parse tree created by the SpiderMonkey engine. All analysis is performed by running JavaScripts.

More info on JShydra click here

I must admit, it has been a slow process getting started (It has been a while since I've had to package something).

There is no actual source tar file of JShydra out there, so I went into the GERMANY cdot machine and found jshydra on there. I created a tar file of the directory and moved the tar file over to my home directory under rpmbuild/SOURCES.

Using the INSTALLING JSHYDRA page off of Mozilla's developer site I started the SPEC file.

Issue #1 (Where I am currently stuck on...)

http://pastebin.org/100264

I will be blogging again as soon as I find a solution....